Breach Response Data Management System and Method

ABSTRACT

An incident is created in response to a cyber event. One or more authorities are identified. At least some of the one or more authorities are associated with respective authority conditions and at least some of the respective authority conditions are associated with respective attributes. Satisfaction of the respective authority conditions of an authority identifies the authority. At least some of respective attributes are associated with the incident as incident attributes. Incident attribute values are received from a user for at least some of the incident attributes. Tasks are identified responsive to at least one of the incident attribute values satisfying respective task conditions of the identified tasks. The tasks are then associated with the incident.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation-in-part of U.S. patent application Ser. No. 17/559,409, filed Dec. 22, 2021, which is a continuation of U.S. patent application Ser. No. 16/400,298, filed May 1, 2019 (now U.S. Pat. No. 11,244,045), which claims priority to and the benefit of U.S. Provisional Application Patent Ser. No. 62/779,835, filed Dec. 14, 2018, the entire disclosures of which are hereby incorporated by reference.

TECHNICAL FIELD

This disclosure relates to, in general, data and system security and more specifically to managing and responding to data breaches and cyber security events.

BACKGROUND

Computing environments, devices, infrastructures, and systems (collectively “systems”) are frequently subject to adverse cyber events (or simply cyber events or incidents). Such cyber events may include malware, phishing, man-in-the-middle, denial-of-service, SQL injection, and the like attacks. At least some such cyber events can result in data breaches due to the unauthorized access and/or disclosure of sensitive, confidential or otherwise protected data. Such data breaches may involve personal health information (PHI), personally identifiable information (PII), trade secrets, or intellectual property. A 2018 Cost of Data Breach Study found that the average total cost to a company of a data breach is $148 per stolen record. The report is accessible at https://www.ibm.com/security/data-breach. Additionally, news stories of cyber hacking and electronic espionage abound. Furthermore, at least some such cyber events may compromise system integrity resulting in significant productivity losses and degraded customer service.

Furthermore, some enterprises (e.g., financial institutions, heath care providers, companies that manage certain user information and that operate in certain jurisdictions) may be subject to regulatory mitigation, controls, and reporting obligations.

Incident threat mitigation involves preventing, collecting, interpreting, analyzing, and acting upon complex data in many forms. This data can describe the attacker, the target user, a system, data, an application, programs, code, communication methods, networks, as well as many other aspects of the computing environment or business operation.

Effective security response management (e.g., response to cyber events) is critical. Effectively detecting system vulnerabilities and anticipating, mitigating, capturing, recording, investigating, acting upon, and responding to security incidents is critical.

SUMMARY

Disclosed herein are implementations of security incident response management.

A first aspect is a method that includes creating an incident in response to a cyber event; identifying one or more authorities, where at least some of the one or more authorities are associated with respective authority conditions, at least some of the respective authority conditions are associated with respective attributes, and where satisfaction of the respective authority conditions of an authority identifies the authority; associating at least some of respective attributes with the incident as incident attributes; receiving, from a user, first incident attribute values for at least some of the incident attributes; identifying tasks responsive to at least one of the incident attribute values satisfying respective task conditions of the identified tasks; and associating the tasks with the incident.

A second aspect is a non-transitory computer readable medium storing instructions operable to cause one or more processors to perform operations that include associating incident attributes with an incident, wherein the incident is created in response to a cyber event; receiving respective values for at least some of the incident attributes; selecting an authority based on one or more authority conditions being satisfied by an incident attribute value of one of the incident attributes; identifying tasks responsive to at least one of the incident attributes values satisfying respective task conditions of the identified tasks; associating the tasks with the incident; transmitting a notification of an assignment of one of the tasks to a user; and receiving, from the user, a completion status of the task.

A third aspect is a device that includes a memory and a processor. The processor is configured to execute instructions stored in the memory to identify a playbook that include tasks and playbook attributes that are based on the cyber event, in response to receiving a cyber event, the playbook; detect a change to a value of one of the playbook attributes; and update the tasks based on the change to the value. To update the tasks includes to remove a first task from the tasks, to close a second task, or to add a third task to the tasks.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure is best understood from the following detailed description when read in conjunction with the accompanying drawings. It is emphasized that, according to common practice, the various features of the drawings are not to-scale. On the contrary, the dimensions of the various features are arbitrarily expanded or reduced for clarity.

FIG. 1 is a block diagram of an example of a computing environment for incident management according to implementations of this disclosure.

FIG. 2 is a block diagram of an example internal configuration of a computing device of the computing environment for incident management shown in FIG. 1.

FIG. 3 is a block diagram of an example of a cyber event response management system according to implementations of this disclosure.

FIG. 4 is an illustration of a user interface of regulations according to implementations of this disclosure.

FIGS. 5A-5B are illustrations of user interfaces of details of regulations of FIG. 4 according to implementations of this disclosure.

FIG. 6 is an illustration of a user interface of a listing tasks associated with an authority according to implementations of this disclosure.

FIGS. 7A-7B are illustrations of user interfaces of details of other authorities according to implementations of this disclosure.

FIG. 8 is an example of a process for responding to cyber events according to implementations of this disclosure.

FIG. 9 is an illustration of a user interface of common incidents according to implementations of this disclosure.

FIG. 10 is an illustration of a user interface of tasks of a playbook according to implementations of this disclosure.

FIG. 11 is an illustration of a user interface of pending tasks according to implementations of this disclosure.

FIG. 12 is an example of a process for responding to cyber events according to implementations of this disclosure.

FIGS. 13A-13B are illustrations of user interfaces for creating incidents according to implementations of this disclosure.

FIG. 14 is a block diagram of another example of a cyber event response management system according to implementations of this disclosure.

FIG. 15 is an example of a process for responding to cyber events according to implementations of this disclosure.

FIG. 16 is an example of a process for an incident in response to receiving a cyber event according to implementations of this disclosure.

FIG. 17 is an example of a process for updating the tasks of an incident and/or playbook according to implementations of this disclosure.

FIGS. 18A-18B illustrate an example of a user interface for creating incidents according to implementations of this disclosure.

FIGS. 19A-19C are illustrations of user interfaces of conditions according to implementations of this disclosure.

FIG. 20 is an illustration of a user interface for creating playbooks according to implementations of this disclosure.

FIG. 21 is an illustration of a user interface of authorities according to implementations of this disclosure.

DETAILED DESCRIPTION

As mentioned above, effective management and response to cyber events is critical. Systems and techniques according to this disclosure can provide effective security response management by enabling security practitioners to effectively anticipate, prevent, mitigate, capture, record, investigate, act upon, respond to, and/or report on security events. The security practitioners can include, for example, legal (e.g., inside and/or outside counsel), compliance, cyber security or computer forensic, IT, managerial, or other personnel. Such systems and techniques enable the tracking of incidents (e.g., cyber events) throughout their life cycles, while continuously keeping an audit trail, sharing knowledge, building learnings, and/or, if required, ensuring regulatory compliance.

Systems and techniques according to this disclosure can enable effective security event (i.e., incident) response. Such systems can learn, aggregate knowledge, share insights, aid investigation, and manage the complete lifecycle of a security event; and facilitate a well-informed response management by integrating, among other information, context-based intelligence feeds (referred to herein as “intel feeds”), integrating relevant controls, and mapping such controls to laws and/or regulations.

Incident investigation can involve collecting, interpreting, analyzing, and acting upon complex data in many forms. These data can describe the attacker, the target user(s), the system(s), the data, the application(s) or program(s), the communication methods, the networks, as well as many other aspects of the computing environment or business operation. Detecting system and/or procedural vulnerabilities and anticipating, mitigating, capturing, recording, investigating, acting upon, and responding to security incidents are referred to as incident management or cyber event management.

To describe some implementations in greater detail, reference is first made to examples of hardware structures.

FIG. 1 is a block diagram of an example of a computing environment for incident management (i.e., a system 100) according to implementations of this disclosure. As used herein, the term “computing environment for incident management,” or variations thereof, can be, or include, a distributed computing system (e.g., a client-server computing system), a cloud computing system, a clustered computing system, or the like.

The system 100 can include one or more customers 102, which may be a public entity, private entity, or other corporate entity or individual that purchases or otherwise uses services of a software provider, such as a platform-as-a-service (PaaS) provider. The customer 102 can include one or more clients. For example, and without limitation, the customer 102 can include a client 104. The client 104 can comprise a computing system, which can include one or more computing devices, such as a mobile phone, a tablet computer, a laptop computer, a notebook computer, a desktop computer, or any other suitable computing device or combination of computing devices. In some implementations, the client 104 can be implemented as a single physical unit or a combination of physical units. In some implementations, a single physical unit can include multiple clients.

The client 104 can be an instance of an application running on a customer device associated with the customer 102. As used herein, the term “application” can include, but is not limited to, applications, programs, instances, processes, threads, services, plugins, patches, application version upgrades, or any other identifiable computing unit capable of accessing or interacting, directly or indirectly, with a database. The system 100 can include any number of customers or clients or can have a configuration of customers or clients different from that generally illustrated in FIG. 1. For example, and without limitation, the system 100 can include hundreds or thousands of customers and at least some of the customers can include or be associated with any number of clients. A customer can include a customer network or domain. For example, and without limitation, the client 104 can be associated or communicate with a customer network or domain.

The system 100 can include a datacenter 108. The datacenter 108 can include one or more servers. The datacenter 108 can be a cloud server provider. In an example, and without limitation, the datacenter 108, as generally illustrated, includes an application server 112 and a database server 116. The system 100 can include any number of datacenters and servers or can include a configuration of datacenters and servers different from that generally illustrated in FIG. 1.

The client 104 and the servers associated with the datacenter 108 may be configured to connect to, or communicate via, a network 106. Furthermore, a client 104 associated with the customer 102 can connect to the network 106 via a communal connection point, link, or path, or using a distinct connection point, link, or path. A connection point, link, or path can be wired, wireless, use other communications technologies, or a combination thereof.

The network 106 can include, for example, the Internet, and/or the network 106 can be, or include, a local area network (LAN), a wide area network (WAN), a virtual private network (VPN), or any other public or private means of electronic computer communication capable of transferring data between a client, such as the client 104, and one or more servers associated with the datacenter 108, or a combination thereof. The network 106, the datacenter 108, or any other element, or combination of elements, of the system 100 can include network hardware such as routers, switches, load balancers, other network devices, or combinations thereof. For example, the datacenter 108 can include a load balancer (not shown) for routing traffic from the network 106 to various servers associated with the datacenter 108.

The datacenter 108 may include an application server 112 and a database server 116. The application server 112 or the database server 116 can be a computing system, which can include one or more computing devices, such as a desktop computer, a server computer, or any other computer capable of operating as a server. In some implementations, the application server 112 or the database server 116 can be non-hardware servers implemented on a physical device, such as a hardware server. In some implementations, the application server 112 and the database server 116 can be implemented as a single hardware server or as a single non-hardware server implemented on a single hardware server. Of course, any number of application servers or database servers can be implemented at the datacenter 108, and the datacenter 108 can include servers other than or in addition to the application server 112 or the database server 116, for example, a web server.

In some implementations, the application server 112 includes an application node 114, which can be a process executed on the application server 112. For example, and without limitation, the application node 114 can be executed in order to deliver services to a client, such as the client 104, as part of a web application. The application node 114 can be implemented using processing threads, virtual machine instantiations, or other computing features of the application server 112. In some implementations, the application node 114 can store, evaluate, or retrieve data from a database, such as the database 118 of the database server 116.

The database server 116 can be configured to store, manage, or otherwise provide data for delivering services to the client 104 over a network. The database server 116 may include a data storage unit, such as a database 118, which can be accessible by an application executed on the application node 114. The database 118 may be implemented as a relational database management system (RDBMS), an object database, an XML database, a CMDB, a management information base (MIB), one or more flat files, other suitable non-transient storage mechanisms, or a combination thereof. By way of non-limiting example, the system 100, in some implementations, can include an XML database. While limited examples are described, the database 118 can be configured as or comprise any suitable database type. Further, the system 100 can include one, two, three, or any suitable number of databases configured as or comprising any suitable database type or combination thereof.

One or more databases (e.g., the database 118), tables, other suitable information sources, or portions or combinations thereof may be stored, managed, or otherwise provided by one or more of the elements of the system 100 other than the database server 116, such as the client 104 or the application server 112.

A distributed computing system can allocate resources of a computer network using a multi-tenant or single-tenant architecture, for example. Allocating resources in a multi-tenant architecture can include installations or instantiations of one or more servers, such as application servers, database servers, or any other server, or combination of servers, that can be shared amongst multiple customers. For example, a web server, such as a unitary Apache installation; an application server, such as a unitary Java Virtual Machine; or a single database server catalog can handle requests from multiple customers. In some implementations of a multi-tenant architecture, the application server, the database server, or both can distinguish between and segregate data or other information of the various customers using the system.

In a single-tenant infrastructure (which can also be referred to as a multi-instance architecture), separate web servers, application servers, database servers, or combinations thereof can be provisioned for at least some customers or customer sub-units. Customers or customer sub-units can access one or more dedicated web servers, have transactions processed using one or more dedicated application servers, or have data stored in one or more dedicated database servers, catalogs, or both. Physical hardware servers can be shared such that multiple installations or instantiations of web servers, application servers, database servers, or combinations thereof can be installed on the same physical server. An installation can be allocated a portion of the physical server resources, such as RAM, storage, communications bandwidth, or processor cycles.

FIG. 2 generally illustrates a block diagram of an example internal configuration of a computing device 200, such as a client 104 or a server, such as an application server 112 or a database server 116, of the system 100 as generally illustrated in FIG. 1. As previously described, a client or server can be a computing system including multiple computing devices or a single computing device, such as a mobile phone, a tablet computer, a laptop computer, a notebook computer, a desktop computer, a server computer, or other suitable computing devices. A computing device 200 can include components or units, such as a processor 202, a bus 204, a memory 206, peripherals 214, a power source 216, a network communication unit 218, a user interface 220, other suitable components, or a combination thereof.

The processor 202 can be a central processing unit (CPU), such as a microprocessor, and can include single or multiple processors having single or multiple processing cores. Alternatively, the processor 202 can include another type of device, or multiple devices, now-existing or hereafter developed, capable of manipulating or processing information. For example, the processor 202 can include multiple processors interconnected in any manner, including hardwired or networked, including wirelessly networked. In some implementations, the operations of the processor 202 can be distributed across multiple physical devices or units that can be coupled directly or across a local area or other suitable type of network. In some implementations, the processor 202 can include a cache, or cache memory, for local storage of operating data or instructions.

The memory 206 can include volatile memory, non-volatile memory, or a combination thereof. For example, the memory 206 can include volatile memory, such as one or more DRAM modules such as DDR SDRAM, and non-volatile memory, such as a disk drive, a solid-state drive, flash memory, Phase-Change Memory (PCM), or any form of non-volatile memory capable of persistent electronic information storage, such as in the absence of an active power supply. The memory 206 can include another type of device, or multiple devices, now-existing or hereafter developed, capable of storing data or instructions for processing by the processor 202. The processor 202 can access or manipulate data in the memory 206 via the bus 204. Although depicted here as a single bus, the bus 204 can be composed of multiple buses, which can be connected to one another through various bridges, controllers, or adapters.

Although shown as a single block in FIG. 2, the memory 206 can be implemented as multiple units. For example, a computing device 200 can include volatile memory, such as RAM, and persistent memory, such as a hard drive or other storage. The memory 206 can be distributed across multiple clients or servers, such as network-based memory or memory in multiple clients or servers performing the operations of clients or servers.

The memory 206 can include executable instructions 208, data, such as application data 210, an operating system 212, or a combination thereof, for immediate access by the processor 202. The executable instructions 208 can include, for example, one or more application programs, which can be loaded or copied, in whole or in part, from non-volatile memory to volatile memory to be executed by the processor 202. The executable instructions 208 can be organized into programmable modules or algorithms, functional programs, codes, code segments, or combinations thereof to perform various functions described herein. For example, the executable instructions 208 can include instructions to manage cyber events as described herein. The application data 210 can include, for example, user files, database catalogs or dictionaries, configuration information or functional programs, such as a web browser, a web server, a database server, or a combination thereof. The operating system 212 can be, for example, Microsoft Windows®, Mac OS X®, Linux®, RIOT, or VxWorks; an operating system for a small device, such as a smartphone or tablet device; an operating system for a large device, such as a mainframe computer; or a derivative of the aforementioned operating systems. The memory 206 can comprise one or more devices and can utilize one or more types of storage, such as solid state or magnetic storage.

The peripherals 214 can be coupled to the processor 202 via the bus 204. The peripherals can be sensors or detectors, or devices containing any number of sensors or detectors, which can monitor the computing device 200 itself or the environment around the computing device 200. For example, a computing device 200 can contain a geospatial location identification unit, such as a global positioning system (GPS) location unit. As another example, a computing device 200 can contain a temperature sensor for measuring temperatures of components of the computing device 200, such as the processor 202. Other sensors or detectors can be used with the computing device 200, as can be contemplated. In some implementations, a client or server can omit the peripherals 214. In some implementations, the power source 216 can be a battery, and the computing device 200 can operate independently of an external power distribution system. Any of the components of the computing device 200, such as the peripherals 214 or the power source 216, can communicate with the processor 202 via the bus 204.

The network communication unit 218 can also be coupled to the processor 202 via the bus 204. In some implementations, network communication unit 218 can comprise one or more transceivers. The network communication unit 218 can, for example, provide a connection or link to a network, such as the network 106, via a network interface, which can be a wired network interface, such as Ethernet, or a wireless network interface. For example, the computing device 200 can communicate with other devices via the network communication unit 218 and the network interface using one or more network protocols, such as Ethernet, TCP, IP, power line communication (PLC), WiFi, infrared, GPRS, GSM, CDMA, or other suitable protocols.

A user interface 220 can include a display; a positional input device, such as a mouse, touchpad, touchscreen, or the like; a keyboard; or other suitable human or machine interface devices. The user interface 220 can be coupled to the processor 202 via the bus 204. Other interface devices that permit a user to program or otherwise use the computing device 200 can be provided in addition to or as an alternative to a display. In some implementations, the user interface 220 can include a display, which can be a liquid crystal display (LCD), a cathode-ray tube (CRT), a light emitting diode (LED) display, (e.g., an OLED display), or other suitable display.

FIG. 3 is a block diagram of an example 300 of a cyber event response management system according to implementations of this disclosure. The example 300 includes a system 302. The system 302 can be employed (e.g., used) by an enterprise (which may be a regulated enterprise, a private entity, a public entity, a governmental agency, a small entity, a large entity, etc.) to continually assess the assets of the enterprise for potential cyber events or vulnerabilities, predict cyber events associated with such assets, respond to a cyber event that has occurred with respect to one such asset, or a combination thereof.

The assets can be computing assets. The computing assets can be hardware, software, telecommunications, or other types of computing assets and/or configurations thereof. Non-limiting examples of computing assets include a Dell server, an Oracle database system, a Tomcat server, and an Apache web server. Non-limiting examples of asset configurations include that the physical server is assigned the IP address 192.168.1.1 and that the server runs the Red Hat Enterprise 6.8, that the Oracle database is configured with 3DES168 encryption, that the Tomcat server AJP port is set to 8100, and that the Apache web server is configured to only accept GET, POST, and HEAD request types.

To aid in the understanding of this disclosure, examples of data and user interfaces are used for illustrative purposes only. The teachings herein are not limited to any specific user interfaces, attributes, task types, classification types, or other data types described herein. The system 302 is described with reference to an enterprise (referred to also as an “instant enterprise”). For example, the system 302 can be considered to be configured with the regulations that apply to the instant enterprise, all the controls (e.g., the IT controls) that apply to or instituted/adopted by the instant enterprise, all the policies that apply to the instant enterprise, relevant contracts that apply to the instant enterprise, other authorities, or a combination thereof. Each of the applicable authorities can be configured with associated tasks.

The system 302 includes a users/groups module 304, an authority module 306, a playbooks module 308, a tasks module 310, and an incidents module 312. The system 302 can include additional or fewer modules. Each of the modules 304-312 can include additional modules and/or the functionality of each of the modules 304-312 can be implemented by submodules. The system 302 can be the application server 112 of FIG. 1. The modules 304-312 can be modules of one or more of the application node 114. The system 302 can be the computing device 200 of FIG. 2. The modules 304-312 can be at least some of the executable instructions 208 of FIG. 2. In the following description, statements that refer to the system 302 as performing an action or a step are to be understood as the action or the step is performed by the system 302, or a module thereof.

The users/groups module 304 provides for the management of users and user groups that participate, to some extent, in the management of cyber events for the instant enterprise. Via the users/groups module 304, users can be assigned permissions and/or responsibilities. Users can be assigned to user groups. Tasks related to cyber events can be assigned to user groups, individual users, roles, or automated agents. For example, a task can be assigned to the Compliance group. For example, a task can be assigned to the user “Jack Bright.” For example, a task can be assigned to the role “CFO.” For example, a task can be assigned to a system (i.e., automated) agent (e.g., a programmed set of instructions that are executable by a processor to accomplish a task). In some situations, an automated agent may not be assigned to a user group. Nevertheless, the automated agent may be referred to as being a member of a user group. For simplicity of reference, and unless otherwise indicated, a user group, a user, a role, or a system agent, are referred to collectively as “user group” or “group.”

As further described below, when a task is assigned to a user group, any user of that user group can accept and/or complete the task. Said another way, the responsibility for completing certain tasks can be delegated to certain groups. As such, only users of the delegated group can complete the task. For example, a task “Mid-year review of GDPR compliance procedures” may be assigned the Compliance group; and a task “Review permissions of all users of the PatientBase system” may be assigned to the administrators user group. When a task related to a cyber event is instantiated, the system 302, or the users/groups module 304, determines, based on attributes of the task, which user group(s) and/or which user(s), the task is to be assigned to (e.g., who can view and/or complete the task). In some implementations, users who are not members of the delegation group can view the task (e.g., can view but cannot modify the details of the task).

The enterprise may be subject to laws and associated regulations; may have contracts with subcontractors, prime contractors, vendors, customers, or the like; may have its own internal policies; or may have defined controls, such as information technology (IT) controls, procedural controls, and so on. Each such law, regulation, contract, IT control, or policy is referred to herein as “an authority.” Such authorities may impose or define requirements related to cyber events. Such requirements can be preventive requirements, configuration requirements, reporting requirements, or other types of requirements.

Such requirements can be codified using the authority module 306. The codification of the requirements determines/establishes what the enterprise is required to do (for example, under at least one authority) to identify and remediate risks, and manage the response process if a cyber event (e.g., a breach) occurs. For example, a set of tasks can be associated with a codified requirement. In some implementations, the set of tasks can be referred to as a playbook or an incident response. The codifying (examples of which are further provided below) can be performed iteratively and/or over an extended period of time. The codification process can be an automated process, a manual process, or a combination thereof.

As mentioned above, the enterprise can have its own controls (such as IT controls) that are designed to ensure that the enterprise's assets (or configurations thereof) and/or procedures are such that cyber events can be avoided, detected, and/or properly responded to. The controls can include preventative controls, detective controls, technical controls, compliance controls, fewer, more, other types of controls, or a combination thereof. A preventative control may be intended to prevent an incident (i.e., a cyber event) from occurring. A detective control may be intended to identify and characterize an incident that may be in progress (i.e., a cyber event that has occurred and is not yet resolved). A technical control may be intended to uncover illegal accesses to an asset of the enterprise. Illegal accesses can be due, for example, to improper user authentication and access control permissions to systems and data within such systems, improper configurations of firewall parameters thereby allowing an actor from outside the instant enterprise to access resources within the instant enterprise. A compliance control can ensure compliance with controls that may be mandated by, for example, privacy laws, policies, and the like.

The enterprise can have policies that define, for example, respective courses of action or procedures related to cyber event (e.g., incident) management. The enterprise may define many types of policies. For example, the enterprise may establish an IT Security Incident Response Policy that defines the responsibilities of a person who reports a security incident (e.g., a cyber event). For example, the enterprise may establish an Information Security Incident Management Policy, which may define the governance and accountability for information security management. For example, the enterprise may establish Critical Incident Management Policies, which may define the development, implementation, and annual review of Critical Incident Management Procedures.

As mentioned, the instant enterprise may be subject to laws and regulations. Such laws and regulations may require the enterprise to institute specific controls to protect certain information types (e.g., PII, PHI, etc.), to process and manage such data in specific ways, and may mandate reporting requirements in cases of cyber events.

The tasks module 310 can be used to manage tasks associated with cyber events. For example, the tasks module 310 can be used to create tasks, which includes assigning tasks to one or more user groups. When an incident is created in the system 302, the tasks module 310 can be used to assign tasks, which are necessary for resolving the incident, to respective user groups. The playbook module 308 can be used to collect a set of tasks into a playbook. A playbook can provide a recipe (e.g., a pre-configured or prespecified set of tasks) for responding to specific incident types. More generally, a playbook can be any collection of tasks. For example, a playbook can be associated with an authority. For example, the collection of tasks that is associated with the GDPR can be referred as a playbook. The tasks of a playbook for responding to an incident can be assembled (e.g., collected, derived) from the tasks of other playbooks. For example, based on the parameters (i.e., attribute values) of an incident, the appropriate (e.g., relevant, related, etc.) tasks from other playbooks can be associated with the tasks for resolving the incident.

The incidents module 312 can be used to manage cyber events. For example, via the incidents module 312, incidents can be created, modified, and resolved. The incidents module 312 can provide mechanisms, such as user interfaces or application programmatic interfaces (e.g., APIs) for the creation of incidents. Workflows and states may be associated with different incident types (for example, based on attribute values of the incidents). The incidents module 312 can be used to shepherd an incident through its associated workflow. The incidents module can be used to ensure that an incident does not advance to a next state in its lifecycle unless certain specified criteria (e.g., gate criteria) are met.

FIG. 4 is an illustration of a user interface of regulations 400 according to implementations of this disclosure. While the regulations 400 are shown in a user interface, it is to be understood that data elements (e.g., records, fields, etc.) associated with each of the displayed regulations (or any data presented in any user interface of this disclosure for that matter) can be stored and managed by the system 302, such as in a database, which can be the database 118 of FIG. 1. In an example, the user interface of regulations 400 can be presented (e.g., generated and managed by) the authority module 306. The regulations 400 shows that the enterprise is subject to four regulations including a regulation 402 and a regulation 404.

The regulation 402 is the New York State Department of Financial Services (NYDFS). The NYDFS is a set of regulations that places cybersecurity requirements on some financial institutions. The stated purpose of the NYDFS is the ensuring a safe and sound financial services marketplace. The requirements imposed by the NYDFS include the encryption of sensitive data, yearly certification of compliance with the regulation, employment of multi-factor authentication, documenting and reporting of cyber security events, and monitoring and limiting the access privileges (e.g., permissions) of users.

The regulation 404 is the General Data Protection Regulation (GDPR). The GDPR imposes requirements on controllers and processors of personal data. According to GDPR, personal data means “any information relating to an identifiable person who can be directly or indirectly identified in particular by reference to an identifier.” A controller is an entity that determines the purposes, conditions and means of the processing of personal data. A processor is an entity, such as a cloud provider, which processes personal data on behalf of the controller. The GDPR, among other requirements, relates to notification policies of companies that have been breached. For example, data breaches, which may pose a risk to individuals, must be notified to the regulators within 72 hours and to affected individuals without undue delay.

FIGS. 5A-5B are illustrations of user interfaces of details of regulations of FIG. 4 according to implementations of this disclosure. A user interface 510 of FIG. 5A and a user interface 550 of FIG. 5B show, respectively, additional data (e.g., attributes) associated with (e.g., defining), respectively, the regulation 402 (i.e., the NYDFS) and the regulation 404 (i.e., the GDPR) of FIG. 4. More, fewer, or other attributes can be associated with a regulation.

The user interface 510 of FIG. 5A shows that the NYDFS regulation has attributes 512-526. The user interface 550 of FIG. 5B shows that the GDPR regulation has attributes 552-566. Each of the attributes 512-526 and 552-566 has a corresponding attribute value. The attribute values can be set during codification of the regulation into the system 302.

The attribute 512 can define the jurisdictional authority that issued the regulation, which is the state of New York in the case of NYDFS.

The attribute 514 defines the controls, if any, that may be implicated by and/or are compliant with the regulation. For example, the NYDFS (i.e., Section 500.16 Incident Response Plan) states that enterprises “shall establish a written incident response plan designed to promptly respond to, and recover from, any Cybersecurity Event materially affecting the confidentiality, integrity or availability of the [enterprise]'s Information Systems or the continuing functionality of any aspect of the Covered Entity's business or operations.” One such industry best practice of a written incident response plan is defined by the National Institute of Standards and Technology (NIST) publication 800-61, titled “Computer Security Incident Handling Guide.” As the instant enterprise has adopted the NIST 800-61 as a control, the user interface 510 illustrates that the NIST 800-61 is a control that is related to the regulation 402 (i.e., the NYDFS).

The attribute 516 can specify the types of incidents (e.g., cyber events) that the NYDFS regulation covers (e.g., is concerned with, inferred to be concerned with, etc.). The incident types that are listed in the attribute 516 can be defined by the instant enterprise. That is, the instant enterprise can define the semantics of the incident types. The incident types of the attribute 516 can be or can be related to incident types that are covered by the NYDFS regulation. The attribute 516 shows that the NYDFS is concerned with cyber events that are of type “Third-party Loss of Theft,” “Loss of Theft of Data,” “Negligence,” “Mistake,” “Illegal Access to Systems or Information,” “Loss or Theft of Equipment,” and “External/Removable Media,” as these incident types are defined by the instant enterprise.

The attribute 518 can specify the types of data that the NYDFS regulation covers (e.g., is concerned with, inferred to be concerned with, etc.). The data classifications that are listed in the attribute 518 can be defined by the instant enterprise. That is, the instant enterprise can define the semantics of the different data classifications. The data classifications of the attribute 518 can be or can be related to data types that are covered by the NYDFS regulation. The attribute 518 shows that the NYDFS is concerned with data that are of type “Personal Information,” “Private Data,” and “Restricted Data,” as these data classifications are defined by the instant enterprise.

The attribute 520 (i.e., event type) can be used to select the user groups assigned (e.g., such as to respond) to an event. For example, an event type of “Low Level” may be assigned only to the IT group. For example, an event type of “Critical” may be assigned to, among others, the legal counsel group. The attribute 520 can be used in combination with other attributes to select (such by the system 302) the assigned groups to an event. The attribute 520, alone or in combination with other attributes, can ensure that the required groups (i.e., members of the groups) are notified in real-time when tasks are assigned to those groups.

The attribute 522 can define the country (or countries) where the regulation is applicable and the attribute 524 can define the state (or states) where the regulation is applicable. The value of the attribute 522 is the “United States” and the value of the attribute 524 is “New York.” The attribute 526 shows any documentation that are relevant to the regulation. The attribute 526 shows that the text of the regulation itself is attached.

With respect to FIG. 5B, the attribute 552 (which is similar to the attribute 512 of FIG. 5A) can define the jurisdictional authority that issued the GDPR regulation, namely the European Union.

The attribute 554 (which is similar to the attribute 514 of FIG. 5A) defines the controls, if any, that may be implicated by the regulation. As the instant enterprise has adopted the NIST 800-61 as a control, the user interface 550 illustrates that the NIST 800-61 is a control that is related to the regulation 404 (i.e., the GDPR).

The attribute 556 (which is similar to the attribute 516 of FIG. 5A) shows that the GDPR is concerned with cyber events that are of type “Loss of Theft of Data,” “Third-party Loss of Theft,” “Negligence,” “Mistake,” “Illegal Access to Systems or Information,” “Loss or Theft of Equipment,” and “External/Removable Media,” as these incident types are defined by the instant enterprise.

The attribute 558 (which is similar to the attribute 518 of FIG. 5A) shows that the GDPR is concerned with data that are of type “Personal Information,” “Health Insurance Data, “Medical Data,” “Private Data,” and “Restricted Data,” as these data classifications are defined by the instant enterprise.

The attribute 560 (which is similar to the attribute 520 of FIG. 5A) shows that the event type is set to “Emergency.”

The attribute 562 (which is similar to the attribute 522 of FIG. 5A) lists the GDPR signatory states, namely the “United Kingdom,” France,” “Spain,” “Germany,” “Austria,” “Belgium,” “Italy,” “Latvia,” “Lithuania,” “Bulgaria, “Luxembourg,” “Croatia,” “Cyprus,” “Malta,” the “Czech Republic,” the “Netherlands Antilles,” “Denmark,” “Poland,” “Estonia,” “Portugal,” “Finland,” “Romania,” “Slovakia,” “Greece,” “Hungary,” “Sweden,” and “Ireland.” The attribute 564 (which is similar to the attribute 524 of FIG. 5A) lists the states of the countries of the attribute 562. The attribute 562 (which is similar to the attribute 526 of FIG. 5A) includes an attached document that is the text of GDPR regulation.

As mentioned above, an authority (a contract, a regulation, a control, etc.) can be codified into the system 302. A user interface control 568 can be used to show the tasks that are codified for an authority. In the case of FIG. 5B, the user interface control 568 can be used to show the tasks that are codified for the regulation 404 of FIG. 4. As mentioned above, the tasks that are codified for an authority can be referred to as the playbook for the authority.

FIG. 6 is an illustration of a user interface of a listing 600 tasks associated with an authority according to implementations of this disclosure. The listing 600 can be displayed in response to initiating (e.g., pressing, selecting, invoking, etc.) the user interface control 568 of FIG. 5B. The listing 600 includes tasks 602-606.

As mentioned, the tasks of the listing 600 includes the codification of at least some parts of the authority. In an example, the Article 33 of the GDPR (titled “Notification of a personal data breach to the supervisory authority”) mandates, in part, the following:

1. In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons. Where the notification to the supervisory authority is not made within 72 hours, it shall be accompanied by reasons for the delay.

2. The processor shall notify the controller without undue delay after becoming aware of a personal data breach.

The above can be codified in the system 302, using the authority module 306, as the tasks 602-604. The task 602 corresponds to the first requirement of the Article 33 section 1, namely the first sentence “In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons.” The task 604 corresponds to the second requirement of the Article 33 section 1, namely the second sentence “Where the notification to the supervisory authority is not made within 72 hours, it shall be accompanied by reasons for the delay.” The task 606 corresponds to the only requirement of the Article 33 section 2, namely that “The processor shall notify the controller without undue delay after becoming aware of a personal data breach.”

Additional details can be associated with each codified task (e.g., the tasks 602-606). In an example, the tasks module 310 can be used to associated details with tasks. For example, a task-details interface 614, which can be displayed when a user interface control 612 that is associated with the task 602 is initiated, indicates which teams 618 (i.e., user groups) are responsible for performing (e.g., resolving, responding to, executing, carrying out, etc.) the task 602 in response to a cyber event that is of a type that is listed in the attribute 556 of FIG. 5B, affects data that are classified as specified by the attribute 558 of FIG. 5B, is of a type as indicated by the attribute 560 of FIG. 5B, implicates the country and/or state as indicated by the attributes 562 and 564, respectively, or a combination thereof. Namely the user groups that are responsible for performing the task 602 are listed as the “Privacy,” “Communications,” “Generate Counsel,” and “Outside counsel” user groups. That is, at least one user from each of the teams listed in the teams 618 is responsible for the completion of the task 602. Alternatively, at least one user from at least one of the teams listed in the teams 618 is responsible for the completion of the task 602.

As another example, a task-details interface 620 that is associated with the task 604 indicates that teams 622 (i.e., user groups) are responsible for performing the task 604. Namely the user groups that are responsible for performing the task 604 are listed as the “Privacy,” “Communications,” “Generate Counsel,” and “Outside counsel” user groups.

FIGS. 7A-7B are illustrations of user interfaces of details of other authorities according to implementations of this disclosure.

As mentioned above, an authority can be a control (such as an IT control). A control details 710 user interface illustrates the details of the NIST 800-61, which is referred to above. The control details 710 illustrates that a control can have attributes that are similar to those of regulations. For example, attributes 716-726 can be similar (e.g., can have the same semantics and values) as the attributes 516-526 as described with respect to FIG. 5A. However, a control can have more, fewer, or other attributes than a regulation. Tasks can also be associated with a control. The tasks associated with a control can be as described with respect the tasks of the listing 600. The control details 710 includes a user interface 728, which can be as described with respect to the user interface control 568 of FIG. 5B.

As also mentioned above, an authority can be a contract. A contract details 750 user interface illustrates the details of a contract titled “Test Contract.” The contract details 750 illustrates that a contract can have attributes that are similar to those of regulations and/or controls. For example, attributes 756-766 can be similar (e.g., can have the same semantics and values) as the attributes 516-526 as described with respect to FIG. 5A. However, a contract can have more, fewer, or other attributes than a regulation or a control. Tasks can also be associated with a contract. The tasks associated with a contract can be as described with respect the tasks of the listing 600. The contract details 750 includes a user interface control 768, which can be as described with respect to the user interface control 568 of FIG. 5B. When the user interface control 768 is invoked, a listing 780 can be displayed. The listing 780 illustrates that a task 782 (with a description of “Alert Vendor of breach”) is to be performed in the case that the instant enterprise is subjected to (e.g., experiences) a data breach. The task 782 can be a contractual obligation that the instant enterprise has to the vendor that is the other party of the contract.

Returning again to FIG. 3, the example 300 illustrates that the system 302 (or modules thereof) can be in communication with zero or more CMDB systems (i.e., a CMDB 320), zero or more procurement systems (i.e., a procurement 322), zero or more intelligence feed systems (i.e., an intel feed 324), zero or more Security Information Event Management systems (i.e., a SIEM 326), zero or more change management systems (i.e., a change management system 328), and/or zero or more source code repository systems (i.e., a source code 330). Examples of procurement systems include SAP ERP, Oracle Procurement, and IBM Emptoris. Examples of change management systems include ServiceNow, BMC remedy, and Hewlett-Packard Service Anywhere. Examples of configuration management systems include ServiceNow, Puppet, Chef, Ansible, BladeLogic, and Microsoft SCCM. Examples of SIEM systems include Splunk, ELK, and LogRhythm. Other systems that the system 302 can be in communication with include record management systems, such as IBM Filenet, Hyland OnBase, EMC Documentum, Opentext ECM, or the like. Examples of source code repository systems include GitHub, Bitbucket and SourceForge. The system 302 can be in communication with other systems such as a credential stores (e.g., Windows Security Accounts Manager, Linux “/etc/shadow,” and Amazon Web Services (AWS) Secrets Manager) for authentication protocols such as Linux PAM (pluggable authentication modules), RADIUS, TACACS, SAMLE, LDAP, oAuth, Kerberos, or other authentication protocols.

The system 302 can use procurement data, change management data, records management data, configuration management data, security incident and event management data, additional data, fewer data, or other data to perform an assessment of such data; determine, based on or using the data, security risks in the context of jurisdictional requirements (for example, as further described below with respect to the authority module 306); and, in response to identifying a security threat, manage the response through a collection (e.g., a playbook) of actions (e.g., tasks) that involve directing changes on endpoint systems/servers/applications/etc. (e.g., configuration items) of a company employing the system 302. The endpoints can be on-premise, cloud-based, networked, or otherwise deployed endpoints.

The CMDB 320 can be comprised of a plurality of configuration items (CIs), attributes associated with the CIs, or relationships between CIs. A CI can be a CMDB record that represents an infrastructure entity, device, or units of the system 100. For example, the customer 102, the client 104, the network 106, the datacenter 108, the load balancer, the application server 112, the application node 114, the database server 116, the database 118, or any other element, portion of an element, or combination of elements of the system 100 can be represented in the CMDB by one or more respective CIs. The CMDB 320 can include information describing the configuration, the role, or both the configuration and the role, of an element of the system 100. In an example, the CMDB 320 can include a CI that represents a database (e.g., an Oracle database). The CI includes information regarding the database. For example, the information regarding the database can include that the database is physically located on a server in New York City, and that the database include financial information regarding clients and client PII information (such as client names, social security numbers, and asset information per client).

The procurement 322 can include features including supplier management, sourcing, requisitioning, purchasing, and payments. The procurement 322 can also include contract management. As such, the procurement 322 can include documents or records regrading contractual obligations. Such contractual obligations can be related to cyber events. As such, by receiving the documents and/or records regarding the contractual obligations, the system 302 can codify and/or can be used to codify contractual obligations related to cyber events of the instant enterprise. In an example, the contract document can be searched for terms such as GDPR, extract sentences that include the verbs “will,” “shall,” “must,” “should,” any variants thereof, or other terms and codify such sentences into the system 302. In an example, the contract can be parsed to identify the required control sets that the instant enterprise must have in place. The required control sets can include preventive controls, requirements for disclosure of a breach, requirements for remediation of a breach, other controls, or combination thereof.

In an example, the system 302 can deconstruct the contract language; map the contract language to other codified requirement (such as codified regulations); determine what controls (e.g., IT controls) should be in place; and match controls against configuration management information. For example, if asset information received from a configuration management system does not satisfy the required controls, then the system 302 can identify such assets, report the assets, and/or created incidents with respect to these assets.

For example, when a new contract agreement becomes active in the procurement 322, the system 302 (or a component thereof) can scan the agreement to determine the jurisdictions that require coverage (e.g., in terms of cyber event monitoring and response) and, e.g., the playbooks. Playbooks and/or tasks can be (e.g., automatically or manually) added, deleted, or changed to provide the contract-required coverage for breach incident responses and reporting for the jurisdiction.

In an implementation, an authority (e.g., a contract, a regulation, etc.) can have an effective date. The effective date can be the date that the authority becomes active or is in full force. As such, in some implementations, a task for responding to an incident of an authority that is not yet active may not be triggered (e.g., initiated, assigned to a user group, etc.) unless the incident date (e.g., date of occurrence of the incident) is on or after the effective date of the authority.

In an implementation, the system 302 can maintain versions of the same authority. For example, a first version of a contract may be effective on Jan. 2, 2018 and a second version of the contract, which amends the first version, may be effective on Sep. 15, 2018. The system 302 can, and/or can provide facilities or tools to, identify differences between two (e.g., versions of) authorities and update playbooks based on the differences. In an example, updating playbooks can include creating a new playbook from an existing playbook such that the new playbook reflects the differences in the authorities. The updated playbooks can included additions, deletions, or edits to the tasks of the original playbook.

For example, assume that a first playbook (K1 PB) of a first version of a contract includes a first task (K1 T1), a second task (K1 T2), and a third task (K1 T3). The first task (K1 T1) is included in the playbooks of a first incident type (I1 PB) and a second incident type (I2 PB), the second task (K1 T2) is included in the playbook of the second incident type (I2 PB); and the third task (K1 T3) is included in the playbook of the first incident type (I1 PB). The contract is now revised to a second version resulting in a second playbook (K1′ PB). The second playbook can be a version of the first playbook (K1 PB).

Based on identifying differences (e.g., textual differences) between the first version and the second version of the contact, it may be determined that (K1 T1) is no longer applicable to the second version of the contact and, as such, it should be removed. Accordingly updated versions of first and the second incident types playbooks (I1′ PB and I2′ PB) are updated to remove K1 T1; it may be determined that the second task (K1 T2) is to be updated to (K1′ T2′); and it may be determined that a new task (K1′ T4) is to be added and further that (K1′ T4) should be added to the updated playbook of the first incident type. Such changes can be made to the existing playbooks without having to create new playbooks from scratch. Table I illustrates which tasks are associated with which playbooks (I1 PB) and (I2 PB) at identified based on the first version of the contact. Table II illustrates which tasks are associated with the updated playbooks (I1′ PB) and (I2′ PB), which may be versions of the playbooks (I1 PB) and (I2 PB), based on the second version of the contract.

TABLE II I1′ pb I2′ PB K1 T1 K1′ T2′ X K1 T3 X K1′ T4 X

TABLE I I1 PB I2 PB K1 T1 X X K1 T2 X K1 T3 X

The intel feed 324 can be an incoming stream of information related to potential or current threats (i.e., cyber events) that the system 302 is managing or is configured to identify and manage. As such, in an implementation, the system 302 may be configured to receive intelligence items from the intel feed 324. One or more modules of the system 302, such as an intel feed module (not shown) can process the intelligence items and associate at least some of the intelligence items with security incidents, tasks, or other information that are currently active (e.g., being mitigated, monitored, or the like) in the system 302 (i.e., by at least one module of the system 302). In an implementation, the system 302, or a module thereof, can crawl the intel feed 324 to extract the intelligence items. In an implementation, the system 302 can subscribe to receive intelligence items from the intel feed 324.

An illustration of using the intel feed 324 is now provided. A cyber event related to an email system has been identified and a playbook (as further described below) is being executed to respond to (e.g., resolve, mitigate, etc.) the cyber event. In the process of carrying out the response (e.g., executing the tasks of the playbook) to the cyber event, a task may be assigned to a user of the users/groups module 304. The system 302 can automatically identify for the user any intel items (e.g., stories, resolution techniques, mitigation techniques, etc.) from intel feeds related to the cyber event and the email system. As such, the user can leverage industry-wide (e.g., internet-wide and/or, more specifically, cyber-security-industry wide) knowledge regarding the cyber event thereby enabling the user to more efficiently and expeditiously resolve (e.g., respond to) the cyber event and complete the task. In an example, the relevant item items can be presented to the user in a user interface that is related to the task that is assigned to the user. In an example, a relevant intel item may be presented to the user as a hyperlink, which, when clicked (e.g., selected) by the user, can navigate the user to a full description of the intel item.

In an implementation, the system 302 can receive (e.g., in real-time, in near real-time, on a scheduled basis, by pull, etc.), from the SIEM 326, analysis of security alerts generated by applications and network hardware. In an example, the system 302 can receive aggregated log data, correlated data, alerts based on analysis of aggregated and/or correlated data, more or fewer data types, or a combination thereof from the SIEM 326.

In an example, the SIEM 326 system can programmatically create (such as via an API of the system 302) an incident in the system 302. In an example, the SIEM 326 can specify the name of a playbook and/or other values for attributes of the incident. The programmatically created incident can be accessed and worked on (such as by completing tasks) by users of the system 302. In another example, a programmatically created incident by the SIEM 326 can cause the system 302 to automatically create a request (e.g., a ticket) in the CMDB 320, the change management system 328, or some system.

An illustration of using the SIEM 326 is now provided. The system 302 (or a module thereof) can receive an event from the SIEM 326, indicating, for example, that data was extracted (e.g., such as via a SQL query) from a database and that the request to extract the data was initiated from a certain Internet Protocol (IP) address. The event may include additional information regarding the database. Such information can be used by the system 302 to determine whether security controls are associated with the database.

In an example, the system 302 can query the CMDB 320 to determine whether the database is configured for encryption. This is so because a control may be that “personally identifiable information must be encrypted at rest.” In another example, whether the database is configured for encryption may be information that is already available to the system 302. If the database is configured for encryption, then the extracted data may be in encrypted format and no serious breach may be considered to have occurred. If the database is determined to not be configured for encryption, then, via the system 302, an incident may be initiated whereby a task can be assigned to the Operator group, which may be set in the system 302 as the user group assigned to the control. For example, the system 302 (or a component thereof) can cause a request (e.g., a support ticket) to be created, for the operator group, in a configuration management system, a change management system, and/or some other system through which tasks can be assigned. The system 302 can receive from such a system an identifier (e.g., a ticket number, a link, etc.) for the created request. The system 302 can also report that the database does not employ encryption in violation of GDPR.

If the system 302 cannot determine whether the database is encrypted, and if the IP address is outside the range of IPs of the instant enterprise, then the system 302 can determine that unencrypted PII data was moved outside the instant enterprise in violation of GDPR. As such, the system 302 can initiate an incidence response, as further described below.

In another example, the system 302 can scan and assess events that are received from the SIEM 326 to determine an updated risk to the instant enterprise of a cyber event. Playbooks and/or tasks can be added, deleted, and/or changed, by one or more components of the system 302, to reflect the updated risk. The system 302 can report changes to risk score of the instant enterprise based on the changes.

An illustration of using the change management system 328 is now provided. Assume that a server is currently configured with an operating system named Lido, version 10. Assume further that a planned upgrade to version 12 is approved in the change management system 328. The system 302 can receive a notification (e.g., an automated notification) of the change. However, based on information received from the intel feed 324, the system 302 includes information regarding known vulnerability of Lido version 12. As such, the system 302 can initiate an incident related to the planned upgrade and/or initiate a notification related to the vulnerability.

An example of using configuration management data from a configuration management system is now provided. Configuration management data can be extracted (e.g., received) from a configuration management system so that the system 302 can perform back testing. Back testing can entail examining how configurations change over time. The changes over time (or at least the most recent and unexamined configuration change) can be compared to an expected security posture. For example, if a change indicates that a firewall setting on an asset (such as a server) of the instant enterprise is changed such that the asset can receive request from outside the enterprise, then a playbook to remediate that vulnerability can be initiated.

In another example, source code from a source code control repository, such as the source code 330 of FIG. 3, can be examined to determine security vulnerabilities. The system 302 can include an interpreter (i.e., a source code analyzer) that can analyze for security vulnerabilities in the source code and/or data that results from the interpreting of the source code. In an example, statistical analysis can be performed on the source code to identify vulnerabilities. The source code analyzer can leverage machine learning tools to combine the source repository along with asset configurations such as policies and network configurations (when available) to determine security vulnerabilities.

FIG. 8 is an example of a process 800 for responding to cyber events according to implementations of this disclosure. The process 800 can be performed by a system, such as the system 302 of FIG. 3. The process 800 can be stored as executable instructions in a memory, such as the memory 206 and/or the executable instructions 208 of FIG. 2. The process 800 can be used to, in the case that a cyber event occurs, respond to (e.g., manage, resolve, communicate about, etc.) as mandated (e.g., required, suggested, recommended, proscribed, etc.) by an authority.

In an implementation, commonly occurring, anticipated, foreseeable, and/or subject to authority (e.g., regulations) cyber events (collectively, common incidents) may be pre-configured. More specifically, responses to such commonly occurring or anticipated cyber events can be pre-configured in the system. Pre-configuration of responses in the system can ensure that the instant enterprise has worked through the most appropriate responses and the set of tasks required to respond to such events.

FIG. 9 is an illustration of a user interface of common incidents 900 according to implementations of this disclosure. The common incidents 900 shows that the instant enterprise has pre-configured responses to five common incidents, including a common incident 902 and a common incident 904. That is, the instant enterprise has preconfigured responses to these common incidents. Each preconfigured response includes a set of tasks. As mentioned above, a task can be assigned to one or more user groups.

The common incident 902 can codify the tasks to be completed when the instant enterprise is breached (e.g., hacked). The common incident 902 is named “NYDFS Playbook.” The common incident 904 codifies the tasks to be completed when a cyber event affecting consumer data of a European Union member state is affected. The common incident 904 is named “GDPR Playbook.” Playbooks codify what the instant enterprise has to do to comply with the regulations, the controls (e.g., IT controls), the internal company policies, the contractual relationships and/or contractual obligations, and/or any other authority as related to cyber events.

The playbooks can be tailored (e.g., created, configured, customized, etc.) to the specific circumstances of the instant enterprise and an incident type. For example, if the instant enterprise is a New York-based enterprise and also serves customers in at least some European Union member states, then a playbook related to data breach can include tasks related to both GDPR and NYDFS. The playbooks can be tailored to the types of events. For example, different tasks may be executed in cases of PII data loss that is due to theft by an employee versus PII data loss that is due to an external hack.

FIG. 10 is an illustration of a user interface of tasks 1000 of a playbook according to implementations of this disclosure. The tasks 1000 illustrate an example of tasks that are associated with a playbook that are related to the ISO 2001 version 2015 standard. In the scope section of the ISO 2001 standard, the standard states: “This International Standard specifies requirements of a quality management system when an organization a) needs to demonstrate its ability to consistently provide products and services that meet customer and applicable statutory and regulatory requirements, and b) aims to enhance customer satisfaction through the effective application of the system, including processes for improvement of the system and the assurance of conformity to customer and applicable statutory and regulatory requirements.” The tasks 1000 more specifically relate to section “7.5.2. Creating and updating [Documented information]” of the standard.

As mentioned above, a playbook can be associated with a cyber event. The cyber event in the example of FIG. 10 can be the regular execution of an ISO 2001 playbook to ensure that documentation requirements of the instant enterprise remain compliant with “applicable statutory and regulatory requirements.” The tasks 1000 includes a task 1002. The task 1002 is assigned to a user group 1004; namely, the “Compliance” group.

At 802, the process 800 receives a cyber event. ‘The cyber event can be at least one of a (real) breach event, a simulation event, or a mitigation event. For example, so that the instant enterprise can test its readiness or completeness of response to a real cyber event, the process 800 can be used to simulate the cyber event by causing the event to be received. In an example, results of the performance of the process 800 can cause the adjustments to a playbook (such as by adding or modifying one or more tasks).

In an example, the cyber event can be received when a user selects a playbook to execute from a list of available playbooks, such as described with respect to FIG. 9. Selecting a playbook can include creating an incident that is pre-configured with a playbook.

In another example, the cyber event can be received from an external system. The external system can be any system that the system 302 communicates with as described with respect to FIG. 3. For example, an event (a trigger, a ticket, etc.) may be received from the CMDB 320 such that the event causes the common incident 904 to be initiated (e.g., instantiated). As such, the cyber event can be received from at least one of a configuration management system, a change management system, a records management system, or a security information and event management system.

In an example, and as described above with respect to intelligence feeds, receiving the cyber event can include receiving an intelligence feed; identifying an asset in a configuration management database based on the intelligence feed; and identifying the cyber event based on the asset.

In an example, receiving the cyber event can include receiving, from a configuration management system, asset information for an asset; identifying, using at least one of the asset information or the asset, a violated policy; and identifying the cyber event in response to identifying the violated policy.

At 804, the process 800 can identify a playbook of tasks. The playbook constitutes a response to the cyber event. As mentioned above, each task of the tasks is assignable to a user group. For example, and continuing from the above example, the event from the CMDB 320 causes the tasks (i.e., the playbook) associated with the common incident 904 to be instantiated and assigned to the respective teams (e.g., user groups). For example, the event received from the CMDB 320 can indicate the assets (e.g., servers, applications, etc.) that experienced (e.g., are affected by) the incident (e.g., the event). Information regarding the affected assets can be used to determine the playbook to be instantiated. For example, the process 800 can access information regarding the asset to determine that the asset manages data from European users. As mentioned above, a task can be assigned to an automated agent. As such, the user can be the automated agent. As such, the user can be a human user or an automated agent.

FIG. 11 is an illustration of a user interface of pending tasks 1100 according to implementations of this disclosure. The pending tasks 1100 displays a list of tasks that a current user (i.e., a user that is viewing the user interface of FIG. 11) can view and/or accept. The current user can accept a task if the user current is a member of a user group to which the task is assigned. In an example, to accept a task, the current user can select an accept 1102 menu action associated with the task. Selecting the accept 1102 menu item can cause a confirmation user interface 1104 to be invoked. In the confirmation user interface 1104, the current user can provide an intended start date 1106, an expected planned end date 1108, and an expected budget 1110 to complete the task. The intended start date 1106 can indicate when the current user intends to start work on the task. The expected planned end date 1108 can indicate when the current user expects to complete the task. The expected budget 1110 can be used to indicate any costs and/or expenditures associated with the task.

At 806, the process 800 can receive from a user, who has accepted a task, a completion indication of the task. In an example, a user interface control associated with a user interface of the task can include a button marked “Completed.” Upon selecting the button, the task can be marked as completed by the process 800. In another example, even if the assigned user marks the task as completed, the task may not be considered completed by the process 800. Completing a task by a user may merely change the status of the task and cause the task to move in a workflow to a next user (e.g., a collaborating user, a reviewing user, etc.). A task may advance through several statuses until the process 800 can consider the task the be completed. At each status, the task may be assigned to different user groups.

At 808, the process 800 can receive a proof of completion of the task. In an example, upon completion of the task by the user, the process 800 can record a timestamp indicating the completion time and date of the task. In an example, the user can also provide proof of completion. For example, the user can associate with (e.g., upload to, attach to, etc.) the task one or more documents, which constitute a proof, a work product, a result, or the like that the user completed the task.

At 810, the process 800 can generate a compliance report. The compliance report can include all information available to the process 800 and which pertain to the tasks of the playbook identified for the cyber event. In an example, the compliance report can be or can be a basis for a final compliance report that is mandated to be provided to a regulatory agency.

In an example, the compliance report can include the assets that were compromised (if any), the chronology of events related to the incident, the classifications of the affected data, one or more of the tasks of the playbook, the list of users who completed each task, completion timestamps of the tasks, or the associated proofs.

In an example, the process 800 can generate the compliance report from a template, such as a document template, for an official notification to the regulatory agency. As the playbook can include tasks assigned to, for example, technical as well as legal personnel, the compliance report can include both technical as well legal information. In an example, a compliance report can include information such as “Server X, located at 4568 Main Street, Suite 10, Anyville, USA 12345, was taken offline on Mar. 4, 2019 at 12:00:56 by the system administrator Joe Black; the backup dated Dec. 12, 2018 was restored the server on Mar. 5, 2019 at 2:20:26; Bill Jobs, COO, notified Jim Jones, COO at Vendor XYZ, of the action on Mar. 5, 2019 at 4:20:4.”

In an example, the process 800 can further include receiving an intelligence feed and associating an intelligence report, from the intelligence feed, with at least one of the playbook of a task of the playbook.

Artificial intelligence and/or machine learning can be used to provide predictions regarding the likelihood and/or impact of future cyber events. The predictions can be based on at least one of back testing of past events using statistical modeling, neural networks, support vector machines, other modeling techniques, or a combination thereof. In an example, predictions can be used to assist cyber insurance providers in assessing the cyber security risks of current or potential insured enterprises. Over time, historical data can be used to predict how certain events translate into costs for an enterprise, and through the enterprise, to costs for its insurance provider. Additionally, systems and methods according to implementations of this disclosure can collect information and provide predictions and insights regarding how systems and types of cyber protections can impact the frequency and damage from various cyber events. For example, such predictions and insights can be generated based on analyses (such as before and after cyber events) of configurations of assets of enterprises as managed in CMDBs, change management systems, and other such systems.

FIG. 12 is an example of a process 1200 for responding to cyber events according to implementations of this disclosure. The process 1200 can be performed by a system, such as the system 302 of FIG. 3. The process 1200 can be stored as executable instructions in a memory, such as the memory 206 and/or the executable instructions 208 of FIG. 2. The process 1200 can be used to, in the case that a cyber event occurs, respond to (e.g., manage, resolve, communicate about, etc.) as mandated (e.g., required, suggested, recommended, proscribed, etc.) by an authority.

At 1202, the process 1200 receives an incident of a cyber event. The incident can be received from a user. The user can be a human user or an external system. At 1204, the process 1200 identifies tasks based on the incident. For example, the process 1200 can identify the tasks based on attribute values of the incident. As mentioned above, each task of the tasks can be assignable to a user group.

In the case of an external system, the system 302 can provide a public API through which the external system can create the incident. An example of the external system can be the SIEM 326, the CMDB 320, or the change management system 328. For example, through the public API, the external system can send information that the system 302 can use to create the incident in the system 302. For example, the information can include an incident name, a description, an IP address of an affected asset, a media access control (MAC) address of the asset, fewer, more, other information, or a subset thereof.

In the case of a human user, the system 302 can provide a user interface, such as user interfaces 1300 and 1350 of FIGS. 13A and 13B, respectively. FIG. 13A is an illustration of the user interface 1300 for creating an incident according to implementations of this disclosure. As the user provides values for some attributes of the incident to be created, the process 1200 can populate the tasks that are required to resolve and/or respond to the incident. The user interface 1300 illustrates attributes 1302-1310. The attribute 1302 indicates the incident type(s), the attribute 1304 indicates the data classification(s) of the data impacted by the incident, the attribute 1306 indicates the event type(s) of the incident, the attribute 1308 indicates the country(ies) where the incident has occurred, the attribute 1310 indicates the state(s) where the incident has occurred.

In an example, a task can be associated with at least one of a particular incident type, a type of data (i.e., a data classification), a particular event type, a specific country, a specific state, other attribute values, or a combination thereof. As such, when the particular attribute value (or a combination thereof) is selected by the user, when using the user interface 1300 to create or modify an incident, then the associated task can be automatically added to the incident.

The user interface 1300 illustrates that the task “ISO Task” is added to a tasks list 1312 upon the user selecting the combination of attribute values “Negligence” (for the attribute 1302), “Personal Information” (for the attribute 1304), “Emergency” (for the attribute 1306), “Afghanistan” (for the attribute 1308), and “Badakhsan” (for the attribute 1310). Contrastingly, the user interface 1350 illustrates that many other tasks are added to a task list 1362 upon the user selecting “Third Party Loss or Theft” and “Illegal Access to System or Information” for incident type (i.e., an attribute 1352), “Personal Information” and “Public Data” for data classification (i.e., an attribute 1354), “Emergency” as the event type (i.e., an attribute 1356), “France” for country (i.e., an attribute 1358), and “Paris” for state (i.e., an attribute 1360).

In an example, the attribute values can be used to identify a violated authority and the violated authority can in turn be used to identify the tasks. As such, identifying, based on the incident, the tasks can include determining a violated authority based on the incident (e.g., one or more of the incident attributes) and identifying the tasks based on the violated authority.

At 1206, the process 1200 receives, from a user of the user group, a completion of the task, as described with respect to the process 800. At 1208, the process 1200 can receive a proof of completion of the task, as described above with respect to the process 800.

In an example, the process 1200 can further include, as described above, receiving a first document constituting an authority; creating one or more playbooks of tasks based on the first document; receiving an second document constituting a revision of the authority; identifying differences between the first document and the second document; and based on the differences, updating at least one of the one or more playbooks of tasks.

FIG. 14 is a block diagram of another example 1400 of a cyber event response management system according to implementations of this disclosure. The example 1400 includes a system 1402. The system 1402 may be employed (e.g., used) by an enterprise to continually assess the assets of the enterprise for potential cyber events or vulnerabilities, predict cyber events associated with such assets, respond to cyber events that occur with respect to such assets, or a combination thereof. The enterprise and assets can be as described with respect to the system 302 of FIG. 3.

When cyber events occur, time is typically of the essence. A resolution or mitigation plan must be identified as soon as possible and as comprehensively as possible. It is critical that implicated authorities and tasks required to respond to cyber events are identified as quickly as possible. The system 1402 includes and implements technical capabilities for expeditiously and thoroughly responding to cyber events. The system 1402 implements and enables a dynamic, rule-based identification of authorities, tasks, playbooks, other object types, or a combination thereof. As more and more data (e.g., facts) related to a cyber event become known (such as based on information gathered or learned, the system 1402 may modify (e.g., add or remove) authorities and/or tasks. To illustrate, a cyber event may be a data breach and the system 1402 may receive (e.g., from user input, accepted from an API, etc.) attribute values for attributes associated with or that describe the cyber event. To illustrate, as a cyber event is further investigated, the number of individuals affected, the jurisdiction where the event occurred, whether the data exposed (e.g., leaked, disclosed, stolen, lost, etc.) was encrypted, or the like, may become incrementally known or refined. Based on these attribute values, the system 1402 can identify the applicable authorities or tasks that may be required. Moreover, when the values of the attributes change over the life of the cyber event or if an authority changes (e.g., a change in a regulation, a new statute passed, etc.), the system 1402 may change which authorities, tasks, or playbooks apply (e.g., are implicated or required).

FIG. 14 is shown as including a CMDB 1420, a procurement 1422, an intel feed 1424, a SIEM 1426, a change management system 1428, and a source code 1430, which may be or may be similar to the CMDB 320, the procurement 322, the intel feed 324, the SIEM 326, the change management system 328, and the source code 330 of FIG. 3, respectively. The system 1402 is shown as including a users/groups module 1404, an authority module 1406, a playbooks module 1408, a tasks module 1410, an incidents module 1412, a conditions module 1414, and an attributes module 1416. The users/groups module 1404, the authority module 1406, the playbooks module 1408, the tasks module 1410, and the incidents module 1412 can be or can be similar to the users/groups module 304, the authority module 306, the playbooks module 308, the tasks module 310, and an incidents module 312 of FIG. 3, respectively. The system 1402 can include additional or fewer modules. Each of the modules 1404-1416 can include additional modules and/or the functionality of each of the modules 1404-1416 can be implemented by submodules. The system 1402 can be the application server 112 of FIG. 1.

To aid in the understanding of the following description, the operations of or examples of workflows enabled by the system 1402 are first described at a high-level.

In an example workflow, an incident may be created in response to a cyber event. Attributes and attribute values may be set (such as by a user) to the incident. The system 1402 uses the incident attributes to evaluate conditions, such as conditions associated with authorities to identify relevant (e.g., matching, triggered, etc.) authorities. By identifying matching authorities, the system 1402 can identify potentially relevant tasks. The system 1402 can additionally use the incident attributes to evaluate conditions (if any) associated with the relevant tasks to identify the relevant and matching tasks that are to be performed (e.g., executed, carried out) in response to the cyber event. If no conditions are associated with a potentially relevant task that is associated with an identified authority, then the system 1402 considers the task to be a matching task that is to be performed. On the other hand, if no conditions are associated with an authority, then the system 1402 does not consider the authority to be relevant to the incident.

In another example workflow, in response to a cyber event, the system 1402 may identify a playbook. The system 1402 may use the identified playbook to identify tasks. The system 1402 may then create an incident and associate the tasks with the incident. In response to detecting a change to a value to an attribute associated with the incident, the tasks associated with the incident nay be updated. The value of the attribute may be changed by the human user or by an automated process.

Conditions (one or more conditions) may be associated with a condition dependent object (CDO). Examples of CDOs include authorities and tasks. In some implementation, conditions may also be associated with playbooks. When the system 1402 determines that a condition associated with a CDO evaluates to true, the system 1402 considers the CDO to be triggered or to be applicable. Conditions use (or are associated with) attributes. A condition is evaluated by substituting an attribute value for the attribute in the condition. The attribute value is obtained from a attribute dependent object (ADO). Conditions may be used by (e.g., assigned to, associated with, configured for, depended on, etc.) CDOs (e.g., authorities or tasks). A CDO can be any object that can be identified based on a condition associated therewith.

Attributes (one or more attributes) may be associated with an ADO. Examples of ADOs include cyber events, incidents, and playbooks. An attribute value may be set for an attribute associated with an ADO. The attributes associated with an ADO are not fixed. That is, attributes on an ADO are not limited to or by any particular set of attributes that may be, for example, fixed by a database schema. Rather, and as described below, attributes can be dynamically created and added (such as by a user) using the system 1402.

In an example, when an attribute value is set for an attribute associated with an ADO, the system 1402 identifies conditions that use the attribute and determines whether the attribute value causes any of the conditions to be satisfied. If a condition is satisfied, the system 1402 identifies CDOs associated with the condition. These identified CDOs are considered triggered (such as for an authority) or required (such as for a task or playbook) by the system 1402. In another example, when a condition is associated with a CDO, the system 1402 can identify ADOs that are associated with an attribute used by the condition. If an attribute value of the attribute of any of the identified ADOs causes the condition to evaluate to true, then the system 1402 considers the CDO to be triggered or satisfied.

Authorities and tasks may be maintained by the authority module 1406 and the tasks module 1410, respectively. Any module that maintains a CDO is referred to herein as “a condition-dependent module (CDM).” Attributes may be used by (e.g., set for, added to, associated with) ADOs (e.g., playbooks or incidents). Playbooks and incidents may be maintained by the playbook module 1408 and the incident module 1412 respectively. Any module that maintains an ADO is an attribute-dependent module (ADM).

The system 1402 can include a library of conditions. The library of conditions can be maintained (e.g., created, updated, processed, evaluated, etc.) by the conditions module 1414. The library of conditions may include at least a subset of all of the conditions defined (e.g., added) using the system 1402. For example, a condition may be defined in such a way that it is to be included in the library of conditions. The library of conditions may be an explicit or an implicit library. That is, the system 1402 may include or manage a library object that includes the conditions (i.e., condition objects) of the library; alternatively, the library of conditions may be obtained (e.g., assembled, generated) as a union of at least some (e.g., all) of the condition associated with CDOs.

Similarly, the system 1402 can include a library of attributes. The library of attributes can be maintained by the attributes modules 1416. The library of attributes may include at least a subset of all attributes defined (e.g., added) using the system 1402. For example, an attribute may be defined in such a way that it is to be included in the library of attributes. The library of attributes may be an explicit or an implicit library. That is, the system 1402 may include or manage a library object that includes the attributes (i.e., attribute objects) of the library; alternatively, the library of attributes may be obtained (e.g., assembled, generated) as a union of at least some (e.g., all) of the attributes associated with ADOs.

A condition, such as one that is included in the library of conditions, can be associated (e.g., assigned to, configured for, used by, etc.) multiple CDOs. Similarly, an attribute, such as one that is included in the library of attributes, can be associated with multiple ADOs. That is, a condition, an attribute, or both can be associated with more than one CDO or ADO, respectively. This allows for each condition (e.g., a definition therefor) or attribute (e.g., a definition therefor) to be entered within the system 1402 and maintained in (e.g., reused from) a central location (e.g., the library, which may be an explicit or an implicit library). Additionally, CDOs and ADOs that use a particular condition and attribute, respectively, can be readily identified therewith shortening incident response time, as described herein. A condition may use one or more attributes; and an attribute may be used by more than one condition. A condition associated with a CDO may be matched (e.g., evaluated, satisfied) using the associated attribute(s) assigned to an ADO.

To reiterate, the conditions module 1414 can be used to define (e.g., set, configure, describe, etc.) conditions. At least some (e.g., all) of the conditions added within the system 1402 can be added to the library of conditions. Conditions added to the library of conditions can be used by CDMs, assigned to CDOs, or both. As such, the conditions module 1414 can be said to handle (e.g., process, evaluate, store, instantiate, etc.) conditions for CDMs, CDOs, or both.

When a condition is to be configured to or by a CDM, the condition can be obtained (e.g., instantiated, constructed, resolved, created, copied, etc.) from the conditions module 1414. As such, and as already stated, the library of conditions can be considered a central repository of conditions that enables condition reuse. For example, and as becomes apparent from the description below, a condition may be used by one or more authorities, one or more tasks, and any other CDO.

A condition may be assigned to a CDO indicating, at least partially, when the CDO may be applicable to (e.g., implicated by or triggered by) a cyber event. As such, a condition can be considered to be a requirement, a pre-requisite, a rule, or a trigger for the CDO. That is, a condition can be, include, or represent a logical requirement that must be satisfied for a CDO to be applicable to an incident (or, equivalently, a cyber event). A CDO may be associated with multiple conditions. The set of conditions associated with a CDO can be referred to as satisfaction criteria. To illustrate, a set of conditions (e.g., satisfaction criteria) that is associated with an authority may include the following conditions indicating when a cyber event (or, equivalently, an incident) triggers the authority: a first condition that the cyber event (or incident) is related to a particular jurisdiction (e.g., municipality, state, nation, etc.), a second condition that the cyber event is related to certain data types (e.g., PII, PHI, etc.), a third condition that the data was not encrypted (e.g., encrypted at rest, encrypted in transit, etc.), a fourth condition that a certain minimal number of user records are affected, another condition, or a combination thereof that can be evaluated.

A condition is evaluated to determine whether the condition is true or false. A condition may be or may be considered to be a hypothesis to be tested. A condition may be defined (expressed) using attributes (further described below). A condition may be expressed or provided using Boolean operators, Boolean expressions, custom expressions, other types of expressions, or a combination thereof. To illustrate, a Boolean expression may be num_records≥500, where the Boolean expression is associated with (e.g., defined for set for, assigned to, etc.) a particular authority, where num_records is an attribute (e.g., a definition of an attribute or an object representing or indicative of the attribute). The attribute num_records may be, for example, associated with a cyber event and may be assigned a value (e.g., 1438 or some other positive integer value). The condition num_records≥500 indicates that if a number of records impacted by a cyber event is greater than or equal to 500, then the particular authority is considered applicable to the cyber event.

As another illustration, determining whether an authority is impacted may require more complicated logic than can be expressed using simple expressions. As such, a condition may be given as an executable function. To illustrate, a function that returns a Boolean value may be IsApplicableBasedOnCount(num_records), where IsApplicableBasedOnCount is the name of a custom function that may be implemented in any number of ways, programming techniques, or programming languages supported by the system 1402. Boolean expressions can also be or use regular expression matching, set operations, or any other expression that can be evaluated to true or false. To illustrate, a Boolean expression may essentially state data_security contains at least one of (‘Encrypted’, ‘Obfuscated’), where data_security is a multi-valued attribute and the expression is used to evaluate whether the list of values of the data_security variable includes at least one of the values ‘Encrypted’ or ‘Obfuscated’.

To be clear, and as further described herein, when an attribute is associated with an ADO, an attribute value of the attribute is said to be assigned to the ADO; and when an attribute is associated with a condition, a criterion of the condition is used for matching against attribute values of ADOs that use the attribute. To illustrate, assume that the num_records attribute, associated with a first incident and a second incident, has the attribute values 67, and 1245, respectively. Assume further that a condition associated with an authority states that num_records>500 (i.e., a criterion of “>500”). As such, the second incident triggers the authority, but the first incident does not trigger the authority.

Conditions may be added to the system 1402 by an authorized person (e.g., an administrator of the system 1402 or portions thereof). In an example, the authorized person can add conditions using user interfaces of the system 1402, such as user interfaces 1900,1950, and 1970 of FIGS. 19A, 19B and 19-C, respectively. Additionally, or alternatively, conditions may be entered into the system via loading tools, such as from a text file.

FIG. 19A is an illustration of the user interface 1900 for listing conditions currently entered within the system. The user interface 1900 illustrates conditions of a library of conditions. FIG. 19B is an illustration of the user interface 1950 that includes a portion 1952 of a user interface for adding conditions and a portion 1958 of a user interface for editing conditions. The user interface 1900 illustrates that multiple conditions have been defined for use within the system 1402, including a condition 1902 and a condition 1904. The condition 1902 includes an attribute labeled “Acted on Good Faith,” which has a data type of Boolean (i.e., the possible values for this attribute are True and False). The condition 1904 includes an attribute labeled “Data Access” such that the value of the attribute is constrained to be one of the values of the list Accessed, Acquired, or None.

Conditions may include other conditions. That is, conditions can be nested and/or can be grouped with other conditions. To illustrate, a condition may be (num_records>1000 AND jurisdiction is in (“US”, “EP”, “JP”)). Two attributes are associated with this condition; namely, num_records and jurisdiction, which are associated with the criteria >1000 and is in (“US”, “EP”, “JP”) (i.e., the jurisdiction value is one of the “US”, “EP”, “JP”), respectively. As another example, a condition may be ((num_records>1000 AND state=‘AL’) OR (num_records>500 AND state=‘AK’)). FIG. 19C illustrates nested and grouped conditions. A condition 1970, which may be associated, for example, with an authority, can be read as “the attribute labeled Data Accessed, which is a multi-valued attribute, includes either of the values ‘Accessed’ or ‘Acquired’ AND the attribute labeled Incident Type, which is also a multi-valued attribute, includes either of the values ‘Denial of Service’, ‘Loss or Theft’, ‘Malicious Code’, and so on.

An element 1954 indicates a condition name. The condition name may be the label of an attribute used by the condition. A condition can have a name that is different from the labels of any of the attributes associated with the condition. An element 1956 indicates the condition type, an example of which is described with respect to the portion 1958. The condition type identifies the data type (e.g., Boolean, Numeric, Alphanumeric, List, Country, State, etc.) that is evaluated for this condition. The portion 1958 illustrates that, in the process of editing a condition, an attribute 1960 (labeled “Data Impacted”) can be defined. The values of the attribute 1960 are constrained to be the values indicated in a list 1962. The list 1962 is shown as including at least a first value 1964 and a second value 1966, labeled “Biometric Information” and “Confidential Information,” respectively.

Returning to FIG. 14, as mentioned above, the attributes module 1416 may be used to maintain a list of attributes configured within or using the system 1402. The attributes module 1416 can be used to handle attributes for an ADM. Attributes may be defined using the conditions modules 1414. For example, as conditions are added to the system 1402 (such as shown with respect to the portion 1958), associated attributes may be created and added to the library of attributes. The library of attributes may be used by an ADM to associate one attribute to multiple ADOs.

Attributes may be used to define (e.g., set, describe, or identify) attribute values (e.g., parameters, facts, or data) of a cyber event (e.g., an ADO) and that may be used to identify a response to the cyber event. To illustrate, an attribute may be used to define or identify a jurisdiction affected by the cyber event, an information type involved in the cyber event, whether the data effected are encrypted, and so on.

As can be appreciated from the foregoing, an attribute (i.e., a definition therefor) may have a label, a data type, constraints, configuration, or a combination thereof. For example, an attribute related to (e.g., defining) a jurisdiction may have the label “state,” may have a data type of String, and may be constrained to the list of states of the U.S.A., and may be configured to allow multi-selections from the list of states. The data type can be a simple or a complex data type. An attribute value (or simply a value) may be assigned to (i.e., set for) an attribute that is associated with an ADO. The attribute value must typically have to satisfy the data type, constraints, and configuration of the corresponding attribute. Statements herein such as or similar to “the attribute X meets a condition Y” should be understood to mean that “the attribute value Z of the attribute X meets or satisfies the condition Y” or that “the condition Y evaluates to true using the attribute value Z of the attribute X.” To illustrate an incident may have the attribute labeled num_records with a assigned attribute value of 1000. When evaluating the condition num_records≥500, the value assigned to the attribute num_records of the incident, in this case 1000, will be used. In this case, and as a result, the condition would evaluate to true since 1000 is greater than or equal 500 (1000≥500).

The authority module 1406 can be used to associate conditions with authorities. Associating conditions to authorities may enable the conditions module 1414 to determine (e.g., identify or select) the subset of the authorities that may be applicable to a cyber event. The subset of the authorities may be determined based on the attributes assigned to an ADO. The subset of authorities may be determined by evaluating the satisfaction criteria of the authorities relative to the attributes of the ADO (e.g., incident or playbook).

To illustrate, assume that an authority named “CCPA” has been defined within the system 1402. The authority may have satisfaction criteria that include a first condition Jurisdiction=“California” and a second condition AnnualRevenue >$25,000,000. Assume further that the attribute Jurisdiction and the attribute AnnualRevenue have been assigned to both incidentA and incident B. Assume that the Jurisdiction attribute assigned to incidentA and B, has the attribute values “Michigan” and “California” respectively. Also assume that the AnnualRevenue attribute assigned to incident A and incident B, has the values $30,000,000 and $24,000,000 respectively.

Responsive to the authority being saved, the conditions module 1414 can evaluate the satisfaction criteria on the CDO against at least some of (e.g., all) the ADOs having the matching associated attributes. To evaluate the satisfaction criteria, the conditions module 1414 may substitute the attribute name within the separate conditions, that comprise the satisfaction criteria, with the corresponding attribute value of the ADO. For example, using the authority and incidents from the prior illustration, the condition Jurisdiction=“California” would become “Michigan”=“California” when using the attributes assigned to incident A and “California”=“California” when using the attributes assigned to incident B. The results of these comparisons would be false for incident A and true for incident B.

Since the first condition evaluates to false with respect to or based on incident A, the condition module 1414 would determine that incident A would not trigger or implicate the authority labelled “CCPA”. However, since the first condition evaluates to true with respect to or based on incident B, the second condition must be evaluated. In this case, the condition AnnualRevenue >$25,000,000 would become $24,000,000>$25,000,000 when using the attribute assigned to incident B. The result of this evaluation would be false for incident B. After evaluating the second condition the condition module 1414 would determine that incident B would not trigger or implicate the authority labelled “CCPA.”

As the conditions associated with an authority are updated (such as due or in response to an updated regulation, change in law, new information, etc.), the authorities associated with any given ADO may be reevaluated, using the same process as the initial evaluation as described above, and updated (e.g., added, removed, etc.) from the ADO as determined based on the satisfaction of the conditions by the ADO attributes. Additionally, the conditions may be evaluated to determine whether the authorities associated with the updated conditions are now applicable to additional ADOs. Similarly, The CDOs (e.g., authorities or tasks) that may be applicable to an ADO (e.g., an incident, or a playbook) may also be updated when the attributes associated with the ADO are modified (e.g., updated, added, removed, etc.). The attributes associated with the ADO may be updated in response to receiving new attribute values (i.e., incident attribute values, or playbook attribute values) from a user as described in more detail below.

The task module 1410 of FIG. 14 may be further configured to associate conditions to tasks. Associating a condition to a task enables the conditions module 1414 to identify tasks that may be required in response to (e.g., to respond to) a given cyber event. The conditions module 1414 may use the attributes associated to an ADO (e.g., an incident) to determine what tasks may be required to resolve the cyber event, using the same process as described for authorities above. As the set of conditions (e.g., satisfaction criteria) associated to a task are updated (e.g., added, removed, etc.) the conditions module 1414 may reevaluate what tasks may be required to resolve the cyber event.

The determination of what tasks are required to resolve the cyber event may also be performed in response to receiving updated attributes associated to an ADO. Receiving updated attributes includes at least one of adding attributes, removing attributes, or modifying attributes values. In either case, the tasks associated with the ADO are updated.

When the system 1402 determines that completion of a task is not needed to resolve the incident, the task may be closed. In an example, the task may also be annotated as being no longer required for the cyber event. In an example, a task may be determined as no longer needed in response to a change in the conditions associated to the task or in response to an update to the attributes associated to the ADO (e.g., incident, playbook) such that no condition of the task is satisfied using attribute values of attributes of ADOs currently associated with the task. To illustrate, a task labeled “Notify Supplier” may be associated with a condition num_records≥500. When a cyber event is first discovered and an incident is created, the num_records attribute assigned to the incident might be assigned a value of 1000. This in turn causes the condition associated with the task to evaluate to true indicating that the “Notify Supplier” task must be performed to resolve the incident. As more information is discovered about the incident, the attribute value of the attribute num_records associated with the incident may be updated to 400. This in turn causes the condition num_records≥500 to no longer evaluate to true. As such, the task “Notify Supplier” would be closed and annotated as being no longer required to resolve the incident. In an example, if the task was already completed and is closed, the task may still be annotated as not being required.

FIG. 15 is an example of a process 1500 for responding to cyber events according to implementations of this disclosure. The process 1500 can be performed by a system, such as the system 1402 of FIG. 14. The process 1500 can be stored as executable instructions in a memory, such as the memory 206 and/or the executable instructions 208 of FIG. 2 and that may be executed by a processor, such as the 202 of FIG. 2. The process 1500 can be used to respond in the case that a cyber event occurs.

At 1502, the process 1500 receives a cyber event. The cyber event can be received from a user. The user can be a human user or an external system. Receiving a cyber event can include that a cyber event object is created by process 1500 and stored in a database, such as the database 118 of FIG. 1.

At 1504, an incident is created in response to receiving the cyber event. The incident can be created as described above. At 1506, one or more authorities are identified. At least some of the identified authorities may be associated with conditions. A condition that is associated with an authority is referred to as an “authority condition.” As mentioned above, a condition (e.g., an authority condition) may be associated with one or more attributes. The attribute may be included in an implicit or an explicit library of attributes. For example, the process 1500 can identify one or more authorities associated with conditions from the library of conditions based on attributes (i.e., attribute values therefor) of the incident.

As also mentioned above, an authority can be associated with one or more conditions that may be satisfied by the attributes of the incident. That is, an authority condition may use (e.g., include, refer to, share, etc.) an attribute of an incident. The satisfaction criteria associated with the attribute of the condition is evaluated using the attribute value of the incident or cyber event. That is, the attribute of the condition is substituted by the value of the attribute of the incident in order to evaluate the condition. The attribute may identify, describe, set, or the like characteristics of the incident or cyber event. The condition may include an expression that is evaluated using the attribute values of the incident or cyber event. If the result of that expression is true, then the condition is said to be satisfied.

As mentioned, the cyber event can be received from an external system. For example, the system 1402 of FIG. 14 can provide a public API through which the external system can cause the system 1402 of FIG. 14 to create the incident. Examples of external systems can be the SIEM 1426, the CMDB 1420, or the change management system 1428. For example, through the public API, the external system can send information that the system 1402 can use to create the incident in the system 1402, which the system 1402 may store in a database, such as the database 118 of FIG. 1. The information can include an incident name, a description, an IP address of an affected asset, a media access control (MAC) address of the asset, fewer, more, other information, or a subset thereof.

At 1508, attributes can be associated with the incident (i.e., incident attributes). In an example, the incident attributes can be added from a library of attributes. In the case of a human user, the system 1402 can provide a user interface, such as the user interface 1800 of FIGS. 18A-18B. As attributes are associated with (i.e., added to) the incident, attribute values may be received for at least some of the attributes, at 1510. For example, a user may obtain data from an intel feed 1424 of FIG. 14. The user may extract (i.e., parse, collect) relevant values that will be used as attribute values from the intel feed 1424. These values can be input as attribute values for the current incident using the user interface 1800 of FIG. 18.

At 1512, the incident attributes may be used to identify tasks. The identified tasks are at least relevant (e.g., required) to resolve, or respond, or both to the incident. At 1514, the process 1500 adds the identified tasks to the incident.

FIGS. 18A-18B are illustrate an example of a user interface 1800 for creating an incident according to implementations of this disclosure. The user interface 1800 illustrates metadata 1802-1806 that may be associated with an incident. At least some of the metadata 1802-1806 may be used for matching, as described herein. That is, at least some of the metadata 1802-1806 may be used to identify CDOs, such as authorities, or tasks in the same manner that attributes are used to identify CDOs. The metadata 1802 indicates the incident leader, the metadata 1804 indicates the incident severity, the metadata 1806 indicate type(s).

An attributes section 1808 shows attributes assigned to the incident (i.e., list of attributes), if any. An Add Attribute 1810 button can be used to add additional attributes to the list of attributes. To illustrate, when a user presses the Add Attribute 1810 button, a list of attributes may be displayed to the user and/or the user may be presented with a user interface for searching for and displaying resulting attributes. The user may select one of the displayed attributes to associate with the incident. The user may also provide attribute values for at least some of the attributes.

Matching Tasks 1812 of FIG. 18B displays the tasks currently associated with the incident (i.e., list of tasks). The matching tasks 1812 is part of (e.g., a continuation of, a section of, etc.) the user interface 1800. The Matching Tasks 1812 may include tasks that are explicitly associated to the incident, such as by a user. The Matching Tasks 1812 also includes tasks whose conditions are satisfied by the incident attributes. To illustrate, using the same determination (i.e., evaluation) as described above, the “Notify Supplier” task may have a condition num_records>1000 associated with it. The user may have added an attribute num_records with a value of 1000 to the incident. As a result, the condition module 1414 may identify the “Notify Supplier” task as being applicable to the current incident.

To illustrate, responsive to receiving an attribute and an associated attribute value, the process 1500 may identify conditions that use the attribute and tasks associated with those conditions. Responsive to the conditions of a task being satisfied, the process 1500 associates the task with (e.g., adds the task to) the incident. As such, the task would be displayed in the list of the Matching Tasks 1812. In another example, the attributes of, or associated with, an incident may be used to identify a violated authority, as described above, and the violated authority may in turn be used to identify the tasks. As such, identifying the tasks can include determining a violated authority based on the incident (e.g., one or more of the incident attributes) and identifying the tasks based on the violated authority.

In an example, the process 1500 can further include receiving, from the user, second incident attribute values. The tasks assigned to the incident can be updated based on the second incident attribute values. Updating the tasks assigned to the incident can include at least one removing a first task from the tasks assigned to the incident, closing a second task, or adding a third task to the tasks assigned to the incident. In an example, closing the second task can include annotating the second task to indicate removal of the second task from the tasks, to indicate that the second task is not relevant to the incident, or both.

FIG. 16 is an example of a process 1600 for responding to cyber events according to implementations of this disclosure. The process 1600 can be performed by a system, such as the system 1402 of FIG. 14. The process 1600 can be stored as executable instructions in a memory, such as the memory 206 and/or the executable instructions 208 of FIG. 2. The executable instructions can be executed by a processor, such as the processor 202 of FIG. 2. The process 1600 can be used to respond in the case that a cyber event occurs.

At 1602, the process 1600 receives a cyber event. The cyber event can be received as described above, such as with respect to 1502 of FIG. 15. At 1604, the process 1600 associates attributes (i.e., incident attributes) to an incident in response to receiving the cyber event. The attributes may selected from a library of attributes.

At 1606 the process 1600 receives, such as from a user, attribute values for at least some of the incident attributes. In an example, the process 1600 may present or cause to be presented a list of attributes (such as attributes available in a library of attributes). The list of attributes may be presented (such as in response to the user invoking the Add Attributes 1810 of FIG. 18). The user may select one of the listed attributes, provide an attribute value (e.g., incident attribute value) for the attribute, and cause (such as by invoking a user interface action) the attribute to be associated with the incident. To illustrate, without loss of generality, the process 1600 may receive attribute values defining the jurisdiction (e.g., Alaska, Michigan, Canada, The United States, The European Union, etc.), the type of information exposed (e.g., leaked, disclosed, stolen, lost, etc.) in the cyber event, or any other value or combination of values which can be defined by the system 1402 and used by the conditions module 1414, or the attributes module 1416, or both.

At 1608, the process 1600 selects an authority having one or more conditions being satisfied by the incident attributes, as described above. Responsive to identifying the authorities, the process 1600, at 1610, may identify one or more tasks having conditions satisfied by the incident attributes. At 1612, the identified tasks are associated with the incident. The identified tasks representing the tasks that may be required in response to (e.g., to respond to) the cyber event.

At 1614 the process 1600 transmits a notification to a user that a task has been assigned to them, as described above in process 800 of FIG. 8. The user may then perform the required actions and transmit (such as using a user interface of the system 1402, using an API, etc.) a completion status of the task to the system 1402. At 1616 the process 1600 receives the task completion status from the user. Once a task has been completed, the task may appear on a compliance report, which may be as described above with respect to FIG. 8.

In an example, the process 1600 can include receiving the cyber event. The cyber event may be received (e.g., identified, inferred, selected, etc.) in any number of ways and/or in any number of formats. For example, the cyber event may be received as structured data, as unstructured data, as key/value pairs, in the form of prose, or any other format. The process 1600 may parse the cyber event to identify cyber event attributes and corresponding cyber event attribute values. The process 1600 may associate at least some of the cyber event attributes with the incident as incident attributes having the corresponding cyber event attribute values.

FIG. 17 is an example of a process 1700 for responding to cyber events according to implementations of this disclosure. The process 1700 can be performed by a system, such as the system 1402 of FIG. 14. The process 1700 can be stored as executable instructions in a memory, such as the memory 206 and/or the executable instructions 208 of FIG. 2. The executable instructions can be executed by a processor, such as the processor 202 of FIG. 2. The process 1700 can be used to respond in the case that a cyber event occurs.

At 1702, the process 1700 receives a cyber event. The cyber event can be received as described above. At 1704, a playbook is identified based on the cyber event. As mentioned above, each playbook may have one or more attributes (e.g., playbook attributes) associated therewith. In an example, a playbook may be a predefined list of tasks. In another example, a playbook may be a dynamic list of tasks. That is, the tasks that form the playbook may be a combination of a predefined list of tasks and other tasks that are identified based on attributes associated with the playbook. As such, changing an attribute value of an attribute of a playbook may result in a change to the tasks (at least those that are dynamically added) associated with the playbook.

At least some of the playbook attributes may have attribute values assigned to them. For example, the attribute values may be provided by a user, as described above in process 1500 of FIG. 15. The attributes may be used to identify a set of authorities having conditions being satisfied, as mentioned above. A playbook may include tasks. Completion of at least some of the tasks may resolve (or contribute to resolving) or may be part of a response to an incident associated with the cyber event. At 1706, a change to the playbook attributes may be detected. The change may be received from a user or an automated agent.

In the case of a human user, the system 1402 can provide a user interface, such as user interface 2000 of FIG. 20. FIG. 20 is an illustration of the user interface 2000 for creating, updating, and/or viewing a playbook according to implementations of this disclosure. As the user provides new attributes of the playbook, the process 1700 can detect the changes to the attributes and may update the CDOs (e.g., authorities, tasks) that are associated to the playbook. After detecting the change to the playbook attributes, the process 1700, at 1708, may perform one or more of the following: removing a task 1710, closing a task 1712, or adding a task 1714. The user interface 2000 illustrates metadata 2002-2004. The metadata 2002 indicates the incident severity, the metadata 2004 indicate type(s), Attributes 2006 indicates the attributes assigned to this playbook (i.e., the attribute list), Matching Tasks 2008 indicates the tasks (i.e. the task list) with conditions satisfied by the playbook attributes. A control 2010 may enable the user to modify any aspect of the playbook. A control 2012 may be used by the user to cause the system 1402 to update (e.g., refresh) the tasks 2008 or authorities in response to the user updating the playbook. Additionally or alternatively, the system 1402 may automatically perform the update in response to the modifications.

In an example, closing the second task can include annotating the second task to indicate that the second task is not relevant to the incident. In an example, the process 1700 can further include identifying an authority based on one or more authority conditions being satisfied by the change to the value of one of the playbook attributes and identify a task based on the change to the value of one of the playbook attributes satisfying task conditions associated with the task.

In an example, detecting the change to the value of one of the playbook attributes can include identifying a first authority triggered by the incident or determining that a second authority currently triggered by the incident is no longer triggered by the incident. In an example, the process 1700 can further include generating an incident report that includes that the authority was triggered and the one or more authority conditions being satisfied.

In an example, the process 1700 can further include using the playbook to respond to a cyber event. As described above, a playbook can be thought of as a set of tasks, or an incident response. As such, in the event that a cyber incident occurs, and a playbook has been defined to respond to the cyber event, the playbook can be used to create an incident with attributes and attribute values associated to the incident already populated. Furthermore, the set of tasks required to resolve the incident can be populated from the playbook without requiring the condition module 1414 to determine (e.g., evaluate) what tasks have conditions satisfied by the incident attributes.

FIG. 21 is an illustration of a user interface 2100 of authorities according to implementations of this disclosure. The user interface 2100 displays a list of available (e.g., defined, set up, configured, etc.) authorities. A column 2102 illustrates respective types of the available authorities, a column 2104 illustrates respective numbers of conditions associated with the available authorities, and a column 2016 illustrates respective numbers of tasks associated with the available authorities.

In some implementations, the system 302 or the system 1402 (or component thereof) can perform trend analysis with respect to vulnerabilities, incidents, and other data accumulated by the system 302 or the system 1402 to perform predictive analytics to predict the timing and nature of a future breach.

For simplicity of explanation, the processes 800, 1200, 1500, 1600 and 1700 are depicted and described as a series of steps. However, steps in accordance with this disclosure can occur in various orders, concurrently, and/or iteratively. Additionally, steps in accordance with this disclosure may occur with other steps not presented and described herein. Furthermore, not all illustrated steps may be required to implement a technique in accordance with the disclosed subject matter.

The implementations herein may be described in terms of functional block components and various processing steps. The disclosed processes and sequences may be performed alone or in any combination. Functional blocks may be realized by any number of hardware and/or software components that perform the specified functions. For example, the described implementations may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, look-up tables, and the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, where the elements of the described implementations are implemented using software programming or software elements the disclosure may be implemented with any programming or scripting language such as C, C++, Java, assembler, or the like, with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Functional aspects may be implemented in algorithms that execute on one or more processors. Furthermore, the implementations of the disclosure could employ any number of conventional techniques for electronics configuration, signal processing and/or control, data processing and the like.

Aspects or portions of aspects of the above disclosure can take the form of a computer program product accessible from, for example, a computer-usable or computer-readable medium. A computer-usable or computer-readable medium can be any device that can, for example, tangibly contain, store, communicate, or transport a program or data structure for use by or in connection with any processor. The medium can be, for example, an electronic, magnetic, optical, electromagnetic, or a semiconductor device. Other suitable mediums are also available. Such computer-usable or computer-readable media can be referred to as non-transitory memory or media, and may include RAM or other volatile memory or storage devices that may change over time. A memory of an apparatus described herein, unless otherwise specified, does not have to be physically contained by the apparatus, but is one that can be accessed remotely by the apparatus, and does not have to be contiguous with other memory that might be physically contained by the apparatus.

The word “example” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “example” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word “example” is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X includes A or B” is intended to mean any of the natural inclusive permutations. In other words, if X includes A; X includes B; or X includes both A and B, then “X includes A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Moreover, use of the term “an aspect” or “one aspect” throughout is not intended to mean the same implementation or aspect unless described as such.

The particular aspects shown and described herein are illustrative examples of the disclosure and are not intended to otherwise limit the scope of the disclosure in any way. For the sake of brevity, conventional electronics, control systems, software development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail. Furthermore, the connecting lines, or connectors shown in the various figures presented are intended to represent exemplary functional relationships and/or physical or logical couplings between the various elements. Many alternative or additional functional relationships, physical connections or logical connections may be present in a practical device.

The use of “including” or “having” and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Unless specified or limited otherwise, the terms “mounted,” “connected,” ‘supported,” and “coupled” and variations thereof are used broadly and encompass both direct and indirect mountings, connections, supports, and couplings. Further, “connected” and “coupled” are not restricted to physical or mechanical connections or couplings.

The use of the terms “a” and “an” and “the” and similar referents in the context of describing the disclosure (especially in the context of the following claims) should be construed to cover both the singular and the plural. Furthermore, recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. Finally, the steps of all methods described herein are performable in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate the disclosure and does not pose a limitation on the scope of the disclosure unless otherwise claimed.

The above-described implementations have been described in order to allow easy understanding of the present disclosure and do not limit the present disclosure. To the contrary, the disclosure is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims, which scope is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structure as is permitted under the law. 

What is claimed is:
 1. A method, comprising: creating an incident in response to a cyber event; identifying one or more authorities, wherein at least some of the one or more authorities are associated with respective authority conditions, at least some of the respective authority conditions are associated with respective attributes, and wherein satisfaction of the respective authority conditions of an authority identifies the authority; associating at least some of respective attributes with the incident as incident attributes; receiving, from a user, first incident attribute values for at least some of the incident attributes; identifying tasks responsive to at least one of the incident attribute values satisfying respective task conditions of the identified tasks; and associating the tasks with the incident.
 2. The method of claim 1, wherein the tasks are associated with at least one of the authorities that has one or more respective authority conditions satisfied by the first incident attribute values.
 3. The method of claim 2, further comprising: receiving, from the user, second incident attribute values; and updating the tasks assigned to the incident based on the second incident attribute values, wherein updating the tasks assigned to the incident comprises at least one: removing a first task from the tasks assigned to the incident; closing a second task; or adding a third task to the tasks assigned to the incident.
 4. The method of claim 3, wherein closing the second task comprises: annotating the second task to indicate removal of the second task from the tasks and that the second task is not relevant to the incident.
 5. The method of claim 1, further comprising: transmitting a notification of an assignment of one of the tasks; and setting a completion status of the one of the tasks responsive to an input indicating completion of the task.
 6. The method of claim 1, further comprising: displaying, to the user, a library of attributes.
 7. A non-transitory computer readable medium storing instructions operable to cause one or more processors to perform operations comprising: associating incident attributes with an incident, wherein the incident is created in response to a cyber event; receiving respective values for at least some of the incident attributes; selecting an authority based on one or more authority conditions being satisfied by an incident attribute value of one of the incident attributes; identifying tasks responsive to at least one of the incident attributes values satisfying respective task conditions of the identified tasks; associating the tasks with the incident; transmitting a notification of an assignment of one of the tasks to a user; and receiving, from the user, a completion status of the task.
 8. The non-transitory computer readable medium of claim 7, wherein the incident attributes are selected from a library of attributes.
 9. The non-transitory computer readable medium of claim 7, wherein the operations further comprise: receiving the cyber event; parsing values from the cyber event to identify cyber event attributes and corresponding cyber event attribute values; and associating at least some of the cyber event attributes with the incident as incident attributes having the corresponding cyber event attribute values.
 10. The non-transitory computer readable medium of claim 7, wherein the operations further comprise: receiving, from the user, second respective values for some of the incident attributes; and updating the tasks assigned to the incident responsive to at least some incident attribute values satisfying respective task conditions, wherein updating the tasks assigned to the incident comprises at least one: removing a first task from the tasks assigned to the incident; closing a second task; or adding a third task, from a library of tasks, to the tasks assigned to the incident.
 11. The non-transitory computer readable medium of claim 10, wherein closing the second task comprises: annotating the second task to indicate removal of the second task from the tasks.
 12. A device comprising: a memory; and a processor, the processor configured to execute instructions stored in the memory to: identify a playbook, in response to receiving a cyber event, the playbook comprising: tasks; and playbook attributes based on the cyber event; detect a change to a value of one of the playbook attributes; and update the tasks based on the change to the value, wherein to update the tasks comprises to: remove a first task from the tasks; close a second task; or add a third task to the tasks.
 13. The device of claim 12, wherein to close the second task comprises to: annotate the second task to indicate that the second task is not relevant to an incident created responsive to the cyber event.
 14. The device of claim 12, wherein the processor is further configured to execute instructions to: identify an authority based on one or more authority conditions being satisfied by the change to the value of one of the playbook attributes; and identify a task based on the change to the value of one of the playbook attributes satisfying task conditions associated with the task.
 15. The device of claim 14, wherein to detect the change to the value of one of the playbook attributes comprises to: identify a first authority triggered by an incident created responsive to the cyber event; or determine that a second authority currently triggered by the incident is no longer triggered by the incident.
 16. The device of claim 14, wherein the processor is further configured to execute instructions to: generate an incident report, wherein the incident report includes that the authority was triggered and the one or more authority conditions being satisfied.
 17. The device of claim 14, wherein the third task is associated with the authority.
 18. The device of claim 12, wherein the processor is further configured to execute instructions to: use the playbook to respond to the cyber event; and transmit a notification of an assignment of one of the tasks to a user.
 19. The device of claim 18, wherein the processor is further configured to execute instructions to: set a completion status of the one of the tasks responsive to an input from the user.
 20. The device of claim 12, wherein the change to the value of one of the playbook attributes is received from a user. 